Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f65e8930d114bfb441024acfc33218ebaebc651e694ccf37b9d57653faeb064a

Tx prefix hash: bffb917841d656a504b3324c08d7422f224c7df0124fff49f815e002add1c249
Tx public key: f1eeb220e59f718562f7dee0082a08b7e9bc54dc5a45a2fbc8cc5607abf77f72
Timestamp: 1736973632 Timestamp [UCT]: 2025-01-15 20:40:32 Age [y:d:h:m:s]: 00:154:03:47:25
Block: 1198120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109888 RingCT/type: yes/0
Extra: 01f1eeb220e59f718562f7dee0082a08b7e9bc54dc5a45a2fbc8cc5607abf77f72021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ff23c4c495911a8714267491e5964a5b4d05641cb40a42b0f298cb9ee81bc94 0.600000000000 1684739 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": 1198130, "vin": [ { "gen": { "height": 1198120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff23c4c495911a8714267491e5964a5b4d05641cb40a42b0f298cb9ee81bc94" } } ], "extra": [ 1, 241, 238, 178, 32, 229, 159, 113, 133, 98, 247, 222, 224, 8, 42, 8, 183, 233, 188, 84, 220, 90, 69, 162, 251, 200, 204, 86, 7, 171, 247, 127, 114, 2, 17, 0, 0, 0, 5, 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