Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f63262e6a7c1b94ebfb19f280910877ca272dfce2ac54a7c5a2917a8fc0e855

Tx prefix hash: bb8b10a25d7ca452988f78f5090f1e2d958bd5dfbfefcaf5525dca07c036c4a3
Tx public key: 57d0663555a2fa489820e9f532a86fe9b3cf4da65add7a903d2ea26f1e2489eb
Timestamp: 1618100789 Timestamp [UCT]: 2021-04-11 00:26:29 Age [y:d:h:m:s]: 03:303:04:37:34
Block: 237160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 976701 RingCT/type: yes/0
Extra: 0157d0663555a2fa489820e9f532a86fe9b3cf4da65add7a903d2ea26f1e2489eb0211000000c590ec05ad000000000000000000

1 output(s) for total of 100.505780967000 dcy

stealth address amount amount idx
00: 643dc560ef60771d6acb2f66fcbddd3f2c848b01ff7236520ab905f6b9b18b49 100.505780967000 493466 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": 237170, "vin": [ { "gen": { "height": 237160 } } ], "vout": [ { "amount": 100505780967, "target": { "key": "643dc560ef60771d6acb2f66fcbddd3f2c848b01ff7236520ab905f6b9b18b49" } } ], "extra": [ 1, 87, 208, 102, 53, 85, 162, 250, 72, 152, 32, 233, 245, 50, 168, 111, 233, 179, 207, 77, 166, 90, 221, 122, 144, 61, 46, 162, 111, 30, 36, 137, 235, 2, 17, 0, 0, 0, 197, 144, 236, 5, 173, 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