Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78acbccfc66096f7e7837ea1c5d30f7d6a4b4ddd8e601016484216a378a5bb7b

Tx prefix hash: fdd5755c41399f9041e7950f471c35edb7f848b0fe6b06fa7284509249bb2569
Tx public key: e3450f16fa4c89c6137268d89428f8af2d8fdbd27c058d8afc29196ce1990f22
Timestamp: 1736903371 Timestamp [UCT]: 2025-01-15 01:09:31 Age [y:d:h:m:s]: 00:153:13:34:18
Block: 1197542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109468 RingCT/type: yes/0
Extra: 01e3450f16fa4c89c6137268d89428f8af2d8fdbd27c058d8afc29196ce1990f2202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 942d05b51eaaf6389f4d8d5f35a6356bfb452b2996c8b847da00c7c9854fc741 0.600000000000 1684153 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": 1197552, "vin": [ { "gen": { "height": 1197542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "942d05b51eaaf6389f4d8d5f35a6356bfb452b2996c8b847da00c7c9854fc741" } } ], "extra": [ 1, 227, 69, 15, 22, 250, 76, 137, 198, 19, 114, 104, 216, 148, 40, 248, 175, 45, 143, 219, 210, 124, 5, 141, 138, 252, 41, 25, 108, 225, 153, 15, 34, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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