Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80381a0ab164d53e83364e37a1b6a3e2ee0a46b702c69e4f7a412fafb5995ac1

Tx prefix hash: d59bdbc20c97379cfb7e3a0eca37cfdf960ebeb139fd9fc9147ac33f613e49a9
Tx public key: 9a4e82f2767e7062011bbdd27bdfb0e32aafb927c59e1efd988f33048804ec5d
Timestamp: 1725369111 Timestamp [UCT]: 2024-09-03 13:11:51 Age [y:d:h:m:s]: 00:082:10:07:39
Block: 1102070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58941 RingCT/type: yes/0
Extra: 019a4e82f2767e7062011bbdd27bdfb0e32aafb927c59e1efd988f33048804ec5d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49239528ba2e558e18f12dcd190ff392360a0b83850a5fd6834d254e8fb0b2d2 0.600000000000 1578361 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": 1102080, "vin": [ { "gen": { "height": 1102070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49239528ba2e558e18f12dcd190ff392360a0b83850a5fd6834d254e8fb0b2d2" } } ], "extra": [ 1, 154, 78, 130, 242, 118, 126, 112, 98, 1, 27, 189, 210, 123, 223, 176, 227, 42, 175, 185, 39, 197, 158, 30, 253, 152, 143, 51, 4, 136, 4, 236, 93, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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