Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6935dd2dafaee62a3402f05da0cbd246dea81c5832c18024bba312ebe2bb58f

Tx prefix hash: 8479906ca394b19e314ec47d950fe73a5729175e7a1b3267f5af3b5c0dbb1784
Tx public key: bbb8b5626ff9b3dbe104baa5f35df50b0ba93904c5f3e11ccf184ec16a9324e9
Timestamp: 1694927673 Timestamp [UCT]: 2023-09-17 05:14:33 Age [y:d:h:m:s]: 01:127:18:55:52
Block: 849879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352605 RingCT/type: yes/0
Extra: 01bbb8b5626ff9b3dbe104baa5f35df50b0ba93904c5f3e11ccf184ec16a9324e90211000000144b8f5122000000000000000000

1 output(s) for total of 0.937557966000 dcy

stealth address amount amount idx
00: d3c79f7f6b4b56e90baad5f57899d7fad6ff01b0cda6c6136fc9f0dfdaa1a1c8 0.937557966000 1303565 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": 849889, "vin": [ { "gen": { "height": 849879 } } ], "vout": [ { "amount": 937557966, "target": { "key": "d3c79f7f6b4b56e90baad5f57899d7fad6ff01b0cda6c6136fc9f0dfdaa1a1c8" } } ], "extra": [ 1, 187, 184, 181, 98, 111, 249, 179, 219, 225, 4, 186, 165, 243, 93, 245, 11, 11, 169, 57, 4, 197, 243, 225, 28, 207, 24, 78, 193, 106, 147, 36, 233, 2, 17, 0, 0, 0, 20, 75, 143, 81, 34, 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