Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638b5d82cbbaddbd61e41417a79e98c38a22cf7b95ed82d092c04cb80fa570fb

Tx prefix hash: 9451ce0b9c9058d3641c52514860e73a4f948e12bde77bebff3c491ddedd02e7
Tx public key: 2d77a892a27bc0dde65c5ee3bce983f7794f97d25ef8ee125b83ddc17edaf3c2
Timestamp: 1727207924 Timestamp [UCT]: 2024-09-24 19:58:44 Age [y:d:h:m:s]: 00:060:22:04:16
Block: 1117314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43536 RingCT/type: yes/0
Extra: 012d77a892a27bc0dde65c5ee3bce983f7794f97d25ef8ee125b83ddc17edaf3c202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ff4d9cacdc41ce2d691366f0f90f921befe18845932f1f7c0183c2cca2ba73 0.600000000000 1598107 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": 1117324, "vin": [ { "gen": { "height": 1117314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ff4d9cacdc41ce2d691366f0f90f921befe18845932f1f7c0183c2cca2ba73" } } ], "extra": [ 1, 45, 119, 168, 146, 162, 123, 192, 221, 230, 92, 94, 227, 188, 233, 131, 247, 121, 79, 151, 210, 94, 248, 238, 18, 91, 131, 221, 193, 126, 218, 243, 194, 2, 17, 0, 0, 0, 6, 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