Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5827f7d26f29f373b38a2dd61e5ef3c17263135c05e889f202d6262eaa51a65a

Tx prefix hash: 0efcd1e1d4d2ccd34c1664f161f253f7cf857d76ff30e49e4fc42aa2a037327c
Tx public key: 587fc0d0e45dfcdcafd3a092f6b7335147de85cf013c4f1303bde8b31b5312fb
Timestamp: 1701302550 Timestamp [UCT]: 2023-11-30 00:02:30 Age [y:d:h:m:s]: 01:340:01:09:42
Block: 902536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501916 RingCT/type: yes/0
Extra: 01587fc0d0e45dfcdcafd3a092f6b7335147de85cf013c4f1303bde8b31b5312fb02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.627369716000 dcy

stealth address amount amount idx
00: 5cc0e4a3b90b365349da1a8d833b90751b6617fec9fc18c16475eff955450503 0.627369716000 1359179 of 0

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": 902546, "vin": [ { "gen": { "height": 902536 } } ], "vout": [ { "amount": 627369716, "target": { "key": "5cc0e4a3b90b365349da1a8d833b90751b6617fec9fc18c16475eff955450503" } } ], "extra": [ 1, 88, 127, 192, 208, 228, 93, 252, 220, 175, 211, 160, 146, 246, 183, 51, 81, 71, 222, 133, 207, 1, 60, 79, 19, 3, 189, 232, 179, 27, 83, 18, 251, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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