Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ad06fbb905ff43ac7898fd78a9a17e11a044d6c7bbd997a38c04c24f15eae8

Tx prefix hash: 8b629cbec362efe563d11ad60f1bd28a5cd710686f9c528d0b5efafb7276ae84
Tx public key: f25c04dc79b5740ec855487d041ba89fde67ca7f049f486a1e5fa8d27ae0c16e
Timestamp: 1738443195 Timestamp [UCT]: 2025-02-01 20:53:15 Age [y:d:h:m:s]: 00:292:22:11:43
Block: 1210019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207129 RingCT/type: yes/0
Extra: 01f25c04dc79b5740ec855487d041ba89fde67ca7f049f486a1e5fa8d27ae0c16e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9e582b8114e6411e9670e0058770c34340bde4417344c7cf9e174bdc443022 0.600000000000 1696766 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": 1210029, "vin": [ { "gen": { "height": 1210019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9e582b8114e6411e9670e0058770c34340bde4417344c7cf9e174bdc443022" } } ], "extra": [ 1, 242, 92, 4, 220, 121, 181, 116, 14, 200, 85, 72, 125, 4, 27, 168, 159, 222, 103, 202, 127, 4, 159, 72, 106, 30, 95, 168, 210, 122, 224, 193, 110, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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