Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e34da09f44d32348fdc0cc6c2ee951209cb4254387d02fe9ce9b0fa9a046d6fb

Tx prefix hash: 8c664db7c83bf163523ba9d9dd19603296580946df424ec1ec58317252af34c5
Tx public key: dd9ed305af5b127b9d9a4ada1cf7c41d95bc8ea108832285995d83236e10a89c
Timestamp: 1711391536 Timestamp [UCT]: 2024-03-25 18:32:16 Age [y:d:h:m:s]: 01:010:22:20:12
Block: 986213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268755 RingCT/type: yes/0
Extra: 01dd9ed305af5b127b9d9a4ada1cf7c41d95bc8ea108832285995d83236e10a89c02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6fef370c017324af5e8efa1d7552becec4b8a5305166f42a756631a1d6b0d1 0.600000000000 1446442 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": 986223, "vin": [ { "gen": { "height": 986213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6fef370c017324af5e8efa1d7552becec4b8a5305166f42a756631a1d6b0d1" } } ], "extra": [ 1, 221, 158, 211, 5, 175, 91, 18, 123, 157, 154, 74, 218, 28, 247, 196, 29, 149, 188, 142, 161, 8, 131, 34, 133, 153, 93, 131, 35, 110, 16, 168, 156, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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