Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f48fb4d70437d990601d2f75e089d0232397fe555bd04da17bd616bf27ce486

Tx prefix hash: 74ac0e0ede5e565ab14bc93ef45017e15622e90d6da6354ea3fbfb448fd6504a
Tx public key: eb7c32bc89ea246bcf05cddd93aa36d943eff2600ba2d2a0c10fc55d231e4ba1
Timestamp: 1626587072 Timestamp [UCT]: 2021-07-18 05:44:32 Age [y:d:h:m:s]: 03:163:21:52:31
Block: 296055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 888684 RingCT/type: yes/0
Extra: 01eb7c32bc89ea246bcf05cddd93aa36d943eff2600ba2d2a0c10fc55d231e4ba102110000000aed79a617000000000000000000

1 output(s) for total of 64.127953853000 dcy

stealth address amount amount idx
00: 78bc5f37af5325fa13ae6c8408f9103d9a473c5e806543684d09e221c529f98b 64.127953853000 619853 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": 296065, "vin": [ { "gen": { "height": 296055 } } ], "vout": [ { "amount": 64127953853, "target": { "key": "78bc5f37af5325fa13ae6c8408f9103d9a473c5e806543684d09e221c529f98b" } } ], "extra": [ 1, 235, 124, 50, 188, 137, 234, 36, 107, 207, 5, 205, 221, 147, 170, 54, 217, 67, 239, 242, 96, 11, 162, 210, 160, 193, 15, 197, 93, 35, 30, 75, 161, 2, 17, 0, 0, 0, 10, 237, 121, 166, 23, 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