Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70e52812b57a74a53adf160852a87f4ab25486cb717bb0a6a2a233a9b7d3d87

Tx prefix hash: 9fc9ed515d15b76bb1acf948ccf350e22cd6ab1e63f8530ddfd868976bd68c65
Tx public key: 2d9ad1e43e40b2cc9989d921f64d7c69e1089e64601e2dbfa41791384effbba1
Timestamp: 1639700356 Timestamp [UCT]: 2021-12-17 00:19:16 Age [y:d:h:m:s]: 03:088:15:12:47
Block: 397117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 842096 RingCT/type: yes/0
Extra: 012d9ad1e43e40b2cc9989d921f64d7c69e1089e64601e2dbfa41791384effbba10211000000030af34938000000000000000000

1 output(s) for total of 29.661074762000 dcy

stealth address amount amount idx
00: 7b36c2f0d82ba22e19fdf01ae4d4127345451ad4573172ad221a50a8ec01d4b3 29.661074762000 795633 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": 397127, "vin": [ { "gen": { "height": 397117 } } ], "vout": [ { "amount": 29661074762, "target": { "key": "7b36c2f0d82ba22e19fdf01ae4d4127345451ad4573172ad221a50a8ec01d4b3" } } ], "extra": [ 1, 45, 154, 209, 228, 62, 64, 178, 204, 153, 137, 217, 33, 246, 77, 124, 105, 225, 8, 158, 100, 96, 30, 45, 191, 164, 23, 145, 56, 78, 255, 187, 161, 2, 17, 0, 0, 0, 3, 10, 243, 73, 56, 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