Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f9053568976dee872950b488dfdbe32233af03f70f6fb6bec89e3f988e95d2

Tx prefix hash: 0da610992a903aeaec7bbf62e1ff33d4b52756a47b1272eca287ea782c16dfb9
Tx public key: c3b7c69addd6fe56c963a92554750f2d8a3616b140237d5cd19f7f8eb2bb487a
Timestamp: 1575823716 Timestamp [UCT]: 2019-12-08 16:48:36 Age [y:d:h:m:s]: 05:349:06:00:39
Block: 23326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1393217 RingCT/type: yes/0
Extra: 01c3b7c69addd6fe56c963a92554750f2d8a3616b140237d5cd19f7f8eb2bb487a02110000000a9159db1e000000000000000000

1 output(s) for total of 513.703057948000 dcy

stealth address amount amount idx
00: 94832ccb02f23b319814389f0b350885ff57249b1e411f0c4f1a1c5c3c740639 513.703057948000 37325 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": 23336, "vin": [ { "gen": { "height": 23326 } } ], "vout": [ { "amount": 513703057948, "target": { "key": "94832ccb02f23b319814389f0b350885ff57249b1e411f0c4f1a1c5c3c740639" } } ], "extra": [ 1, 195, 183, 198, 154, 221, 214, 254, 86, 201, 99, 169, 37, 84, 117, 15, 45, 138, 54, 22, 177, 64, 35, 125, 92, 209, 159, 127, 142, 178, 187, 72, 122, 2, 17, 0, 0, 0, 10, 145, 89, 219, 30, 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