Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93607deefba727fca37ae459774ed5c2fc0b5cfc1db9c1d86767b7b5f286a62a

Tx prefix hash: c0daf196ce2f5b4c331db4e98f5d4685100d8d3a6996b233b843faf3cd082633
Tx public key: 9b42953e49f795323c35043c246a10de3b0fe1f906c546ae9850f7af5f96fe17
Timestamp: 1648596189 Timestamp [UCT]: 2022-03-29 23:23:09 Age [y:d:h:m:s]: 02:350:16:06:07
Block: 469204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770007 RingCT/type: yes/0
Extra: 019b42953e49f795323c35043c246a10de3b0fe1f906c546ae9850f7af5f96fe17021100000001a272b9cb000000000000000000

1 output(s) for total of 17.113255043000 dcy

stealth address amount amount idx
00: 2b3a29c278e90ebf189efa52f97ae6224d1a7d3a4ada04786943cdc664f51ed7 17.113255043000 888100 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": 469214, "vin": [ { "gen": { "height": 469204 } } ], "vout": [ { "amount": 17113255043, "target": { "key": "2b3a29c278e90ebf189efa52f97ae6224d1a7d3a4ada04786943cdc664f51ed7" } } ], "extra": [ 1, 155, 66, 149, 62, 73, 247, 149, 50, 60, 53, 4, 60, 36, 106, 16, 222, 59, 15, 225, 249, 6, 197, 70, 174, 152, 80, 247, 175, 95, 150, 254, 23, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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