Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f8d1414241481761d2285e9b464c148786373ab20b358cbd8263d84163e6c4

Tx prefix hash: 123d3fc98723eba36fd65dc2da7c2f5acdfd43ef6c2d92df36dc9831595aa608
Tx public key: dfec4c8974710b4cb06e6951fc0fd237ea11f1903c370a03d345b40fb1ba3ceb
Timestamp: 1703858716 Timestamp [UCT]: 2023-12-29 14:05:16 Age [y:d:h:m:s]: 01:103:10:08:30
Block: 923737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335027 RingCT/type: yes/0
Extra: 01dfec4c8974710b4cb06e6951fc0fd237ea11f1903c370a03d345b40fb1ba3ceb02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2035090ca3cbc7fe4e3beca13be92e01819752d0e0bcbd7e69f119d7471e53a8 0.600000000000 1381473 of 15

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": 923747, "vin": [ { "gen": { "height": 923737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2035090ca3cbc7fe4e3beca13be92e01819752d0e0bcbd7e69f119d7471e53a8" } } ], "extra": [ 1, 223, 236, 76, 137, 116, 113, 11, 76, 176, 110, 105, 81, 252, 15, 210, 55, 234, 17, 241, 144, 60, 55, 10, 3, 211, 69, 180, 15, 177, 186, 60, 235, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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