Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02505a3db07ce5bb7916cff50d80a532bfa478b04b0c96721c8ddc78e5ca1005

Tx prefix hash: e6ce68f35672f04b27c6416acef6105acd9bd831950dc58b4e90e72f8c83d442
Tx public key: d0c0cdfbbd23e4de1d09b77d23db7797088d5916f33ca3e044b7c1f82ddee673
Timestamp: 1696008208 Timestamp [UCT]: 2023-09-29 17:23:28 Age [y:d:h:m:s]: 01:230:21:48:27
Block: 858855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426103 RingCT/type: yes/0
Extra: 01d0c0cdfbbd23e4de1d09b77d23db7797088d5916f33ca3e044b7c1f82ddee67302110000000d4b8f5122000000000000000000

1 output(s) for total of 0.875501513000 dcy

stealth address amount amount idx
00: 8573c005cba918d97664a9b2a17fe20d764bc16bc926a80ab958232beed89c98 0.875501513000 1313053 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": 858865, "vin": [ { "gen": { "height": 858855 } } ], "vout": [ { "amount": 875501513, "target": { "key": "8573c005cba918d97664a9b2a17fe20d764bc16bc926a80ab958232beed89c98" } } ], "extra": [ 1, 208, 192, 205, 251, 189, 35, 228, 222, 29, 9, 183, 125, 35, 219, 119, 151, 8, 141, 89, 22, 243, 60, 163, 224, 68, 183, 193, 248, 45, 222, 230, 115, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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