Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e561eec678aa32068333d4df9998f42a65d4ce74f16d122cf02bdd1c178b670b

Tx prefix hash: 7ac28bcacf259435cc388319d2ad2921cd5d906c4324c88ac78fe796bcdc4be3
Tx public key: 98f2bd742b85c3534b095b9038adc0f04de44b6e47168dbb2f0cffb92c42a66c
Timestamp: 1717240372 Timestamp [UCT]: 2024-06-01 11:12:52 Age [y:d:h:m:s]: 00:237:00:02:33
Block: 1034685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169557 RingCT/type: yes/0
Extra: 0198f2bd742b85c3534b095b9038adc0f04de44b6e47168dbb2f0cffb92c42a66c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb7a2e44d62f4794b9f349770b5eba39e86f34d16858e5d8ba39fdc39637b7b7 0.600000000000 1503202 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1034695, "vin": [ { "gen": { "height": 1034685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb7a2e44d62f4794b9f349770b5eba39e86f34d16858e5d8ba39fdc39637b7b7" } } ], "extra": [ 1, 152, 242, 189, 116, 43, 133, 195, 83, 75, 9, 91, 144, 56, 173, 192, 240, 77, 228, 75, 110, 71, 22, 141, 187, 47, 12, 255, 185, 44, 66, 166, 108, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8