Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee30bad95aaa315c5ad7cfe3b36ece65354010821438f8a01fd8da614f13ec4

Tx prefix hash: 003f0b11e7146d542e02485c560bac22f6ff93f6f7052bb4eefd5dd8d213a589
Tx public key: 3ce60da1eeb9b2dfcdfc95b04480e30d32bcc72ab091bc9cba357914277e8297
Timestamp: 1696818634 Timestamp [UCT]: 2023-10-09 02:30:34 Age [y:d:h:m:s]: 01:175:18:03:15
Block: 865580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386628 RingCT/type: yes/0
Extra: 013ce60da1eeb9b2dfcdfc95b04480e30d32bcc72ab091bc9cba357914277e829702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.831714311000 dcy

stealth address amount amount idx
00: 632b7f3f1994e5f25f83db1b9c2a0075103ff0d275252750315aacb08dfbfc55 0.831714311000 1320118 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": 865590, "vin": [ { "gen": { "height": 865580 } } ], "vout": [ { "amount": 831714311, "target": { "key": "632b7f3f1994e5f25f83db1b9c2a0075103ff0d275252750315aacb08dfbfc55" } } ], "extra": [ 1, 60, 230, 13, 161, 238, 185, 178, 223, 205, 252, 149, 176, 68, 128, 227, 13, 50, 188, 199, 42, 176, 145, 188, 156, 186, 53, 121, 20, 39, 126, 130, 151, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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