Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eabe3335dca71885abdf766701bb93d69056bda8d6760a45ba6121a8b144e483

Tx prefix hash: 0319ce2e2bdd41b05b81f99de6a78feb9d72f3d9ec48e320e3fa5660fe4aad92
Tx public key: 2dd3ffd0754cbf0848fab7431e946dca8a29e42832f92d1c4778c0a6c0c03db9
Timestamp: 1693455321 Timestamp [UCT]: 2023-08-31 04:15:21 Age [y:d:h:m:s]: 01:077:06:30:13
Block: 837665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316530 RingCT/type: yes/0
Extra: 012dd3ffd0754cbf0848fab7431e946dca8a29e42832f92d1c4778c0a6c0c03db9021100000011e6d27f9c000000000000000000

1 output(s) for total of 1.029125166000 dcy

stealth address amount amount idx
00: 6a047439f08a3eb130c6a0b35ca2ebcf7eb8fad49fe71de81200d9503fc17703 1.029125166000 1290315 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": 837675, "vin": [ { "gen": { "height": 837665 } } ], "vout": [ { "amount": 1029125166, "target": { "key": "6a047439f08a3eb130c6a0b35ca2ebcf7eb8fad49fe71de81200d9503fc17703" } } ], "extra": [ 1, 45, 211, 255, 208, 117, 76, 191, 8, 72, 250, 183, 67, 30, 148, 109, 202, 138, 41, 228, 40, 50, 249, 45, 28, 71, 120, 192, 166, 192, 192, 61, 185, 2, 17, 0, 0, 0, 17, 230, 210, 127, 156, 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