Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c37a00e5bcbd49fc0849bcd0ff3f97c268b25f0dee5fe1c4c19d21df5cee3e9

Tx prefix hash: d477f4b3edfba115b08885118ee704da4e9683540405a1538fb01c1bdcfec1c5
Tx public key: 977284c9c7495fcdf3d3d16d40054041b101eba3ae85fd4354b0e8febc788052
Timestamp: 1703621512 Timestamp [UCT]: 2023-12-26 20:11:52 Age [y:d:h:m:s]: 01:103:16:20:09
Block: 921769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335207 RingCT/type: yes/0
Extra: 01977284c9c7495fcdf3d3d16d40054041b101eba3ae85fd4354b0e8febc7880520211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9668dab6d1823e2aa251d8f6bc8f0816e23ebb7a1d09e88b5d243e0bef317e 0.600000000000 1379463 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": 921779, "vin": [ { "gen": { "height": 921769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9668dab6d1823e2aa251d8f6bc8f0816e23ebb7a1d09e88b5d243e0bef317e" } } ], "extra": [ 1, 151, 114, 132, 201, 199, 73, 95, 205, 243, 211, 209, 109, 64, 5, 64, 65, 177, 1, 235, 163, 174, 133, 253, 67, 84, 176, 232, 254, 188, 120, 128, 82, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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