Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef80b047f45b9cbd92eb3fcc832847217e932721acc56ce4a5e9f9e898f6955

Tx prefix hash: 7952682a703975c0dbcd96047ca44bb27c9a9eacb7c36e1e7ea04b3268885192
Tx public key: a416d7d543a85123b2a2290510f9a186ba9d359ab2cea6aa332b99c24e672c91
Timestamp: 1726879976 Timestamp [UCT]: 2024-09-21 00:52:56 Age [y:d:h:m:s]: 01:048:07:04:44
Block: 1114597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292918 RingCT/type: yes/0
Extra: 01a416d7d543a85123b2a2290510f9a186ba9d359ab2cea6aa332b99c24e672c91021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915a29e412e65c5d3cfd153ab7151ffdeeafde23681b8a62746f190911d4e1cf 0.600000000000 1594434 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": 1114607, "vin": [ { "gen": { "height": 1114597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915a29e412e65c5d3cfd153ab7151ffdeeafde23681b8a62746f190911d4e1cf" } } ], "extra": [ 1, 164, 22, 215, 213, 67, 168, 81, 35, 178, 162, 41, 5, 16, 249, 161, 134, 186, 157, 53, 154, 178, 206, 166, 170, 51, 43, 153, 194, 78, 103, 44, 145, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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