Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398853b17db453c5188a3e2cf3f089d50d2be72701046dd93a0543b4b6ffc7eb

Tx prefix hash: 71b00c561fae4b50419d758339994ebe37e45e2987aabaf9fe569078b1d80c3e
Tx public key: 9dff3e1ebced065a321ec9a5e643a5ec403edd9755e7b28369f55f38a9eabdc8
Timestamp: 1722270061 Timestamp [UCT]: 2024-07-29 16:21:01 Age [y:d:h:m:s]: 00:320:19:18:15
Block: 1076370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229137 RingCT/type: yes/0
Extra: 019dff3e1ebced065a321ec9a5e643a5ec403edd9755e7b28369f55f38a9eabdc802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b17880955575474a6ca23f13361316db1631409de2ee91bb752faf60db9a6b6 0.600000000000 1548907 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": 1076380, "vin": [ { "gen": { "height": 1076370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b17880955575474a6ca23f13361316db1631409de2ee91bb752faf60db9a6b6" } } ], "extra": [ 1, 157, 255, 62, 30, 188, 237, 6, 90, 50, 30, 201, 165, 230, 67, 165, 236, 64, 62, 221, 151, 85, 231, 178, 131, 105, 245, 95, 56, 169, 234, 189, 200, 2, 17, 0, 0, 0, 3, 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