Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd00d4428342c9c6ef3b0b7d74df38fdce9c6821ce730d751723c309038b74f2

Tx prefix hash: 066da0a9f3d819a384b3f8cf8d7afcacae3e858de4f1783d6497142bcd7a9ae7
Tx public key: 6134ad8bb1f424ea1f66225262e8c4b8a249cb47ec861f673816d97e74dc7ac0
Timestamp: 1694540893 Timestamp [UCT]: 2023-09-12 17:48:13 Age [y:d:h:m:s]: 01:226:05:05:35
Block: 846674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422762 RingCT/type: yes/0
Extra: 016134ad8bb1f424ea1f66225262e8c4b8a249cb47ec861f673816d97e74dc7ac002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.960766006000 dcy

stealth address amount amount idx
00: 4bc143df0ea7ee908b980e5f12e534dfc6e849928cd76b46d836fe02383cd64f 0.960766006000 1300150 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": 846684, "vin": [ { "gen": { "height": 846674 } } ], "vout": [ { "amount": 960766006, "target": { "key": "4bc143df0ea7ee908b980e5f12e534dfc6e849928cd76b46d836fe02383cd64f" } } ], "extra": [ 1, 97, 52, 173, 139, 177, 244, 36, 234, 31, 102, 34, 82, 98, 232, 196, 184, 162, 73, 203, 71, 236, 134, 31, 103, 56, 22, 217, 126, 116, 220, 122, 192, 2, 17, 0, 0, 0, 3, 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