Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65bb6ed52c04d26a45437bfe21e8a0f167eb13dc4b152ef071fec9439e9ca021

Tx prefix hash: 839199cafee67bd31b16a325fdca901e18327b15a26aedc093077edc47b966aa
Tx public key: d7375cf3e5c4a112be04df7bce08e9b19c0f5ef7d35db2a8901e1d3be598ad82
Timestamp: 1731629597 Timestamp [UCT]: 2024-11-15 00:13:17 Age [y:d:h:m:s]: 01:033:01:41:38
Block: 1153890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282083 RingCT/type: yes/0
Extra: 01d7375cf3e5c4a112be04df7bce08e9b19c0f5ef7d35db2a8901e1d3be598ad8202110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a5908b799fea37587acd89f519caf8d70524e79d0a4b7be70126b616357685 0.600000000000 1639501 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": 1153900, "vin": [ { "gen": { "height": 1153890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a5908b799fea37587acd89f519caf8d70524e79d0a4b7be70126b616357685" } } ], "extra": [ 1, 215, 55, 92, 243, 229, 196, 161, 18, 190, 4, 223, 123, 206, 8, 233, 177, 156, 15, 94, 247, 211, 93, 178, 168, 144, 30, 29, 59, 229, 152, 173, 130, 2, 17, 0, 0, 0, 12, 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