Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31661937ab81351db8026e32d5c6071f63bde05e99e0a13b1a6369b6a3e6f25d

Tx prefix hash: 62bdb44165c94ca6c7d5719f307d7d299b49792d20646a567e815741a93c8319
Tx public key: dcf6fabc1fae7b48f81a7e62591b89c4a9041cfe347cf6a3d2fdcafe3a20129c
Timestamp: 1712916578 Timestamp [UCT]: 2024-04-12 10:09:38 Age [y:d:h:m:s]: 00:362:21:34:13
Block: 998803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259472 RingCT/type: yes/0
Extra: 01dcf6fabc1fae7b48f81a7e62591b89c4a9041cfe347cf6a3d2fdcafe3a20129c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b5221df0e556aeddcc2f9e201ede345b58df57dd4b02164d925fabadf03a569 0.600000000000 1459263 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": 998813, "vin": [ { "gen": { "height": 998803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b5221df0e556aeddcc2f9e201ede345b58df57dd4b02164d925fabadf03a569" } } ], "extra": [ 1, 220, 246, 250, 188, 31, 174, 123, 72, 248, 26, 126, 98, 89, 27, 137, 196, 169, 4, 28, 254, 52, 124, 246, 163, 210, 253, 202, 254, 58, 32, 18, 156, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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