Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de1d3f14f808a9ed7649f9fd3c4bb50b17e4cb3f112e768858a9f79803f4ef8

Tx prefix hash: 9b4f40f56289227a04aaee4bc5c84da0a5023916ba508925ab1c1e3d52f19d0d
Tx public key: 93da9d421ce1aa1687788321a5c61f141aa0a7e41f34561e3e0e3e8a0d1e283f
Timestamp: 1707691247 Timestamp [UCT]: 2024-02-11 22:40:47 Age [y:d:h:m:s]: 01:015:08:24:40
Block: 955498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271983 RingCT/type: yes/0
Extra: 0193da9d421ce1aa1687788321a5c61f141aa0a7e41f34561e3e0e3e8a0d1e283f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6017772c45d9b6c08992cd0afda26b04a371f2caa102502e8377a9a357a5a123 0.600000000000 1414788 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": 955508, "vin": [ { "gen": { "height": 955498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6017772c45d9b6c08992cd0afda26b04a371f2caa102502e8377a9a357a5a123" } } ], "extra": [ 1, 147, 218, 157, 66, 28, 225, 170, 22, 135, 120, 131, 33, 165, 198, 31, 20, 26, 160, 167, 228, 31, 52, 86, 30, 62, 14, 62, 138, 13, 30, 40, 63, 2, 17, 0, 0, 0, 2, 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