Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e13cf42fbb429fbe520902c42817603056365b911dfa10c7416ae07ecbc315

Tx prefix hash: cb36b16fc37241ca4f932dae09e51710a8130b27d54600f6f3bdff53be3422c1
Tx public key: c9c077f9dfef786e2028a37de4a9e77904079e974ae95c4174bb47d28389590d
Timestamp: 1728100630 Timestamp [UCT]: 2024-10-05 03:57:10 Age [y:d:h:m:s]: 00:179:23:38:46
Block: 1124710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128421 RingCT/type: yes/0
Extra: 01c9c077f9dfef786e2028a37de4a9e77904079e974ae95c4174bb47d28389590d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8dc9e77de1c78a52be70f2b9b55ba3d7729c0316647d2ceff0a857cd8eab0a5 0.600000000000 1607375 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": 1124720, "vin": [ { "gen": { "height": 1124710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8dc9e77de1c78a52be70f2b9b55ba3d7729c0316647d2ceff0a857cd8eab0a5" } } ], "extra": [ 1, 201, 192, 119, 249, 223, 239, 120, 110, 32, 40, 163, 125, 228, 169, 231, 121, 4, 7, 158, 151, 74, 233, 92, 65, 116, 187, 71, 210, 131, 137, 89, 13, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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