Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c289e61bf438058b0422dd38c7c74ebad3cae7ef424dff9538a644b006c2d7

Tx prefix hash: a889e7c9c2019d6309969c0dd3c3a94ff527ba07bc8fd9b8ff1d6b5e0789fd1a
Tx public key: 0da10826aa83f7a43f19f3a428e906bc4400f859f34f1ca2b366e357ca245158
Timestamp: 1711958212 Timestamp [UCT]: 2024-04-01 07:56:52 Age [y:d:h:m:s]: 01:016:03:41:54
Block: 990852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272543 RingCT/type: yes/0
Extra: 010da10826aa83f7a43f19f3a428e906bc4400f859f34f1ca2b366e357ca2451580211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c8e6cdcba547034fafa18c425d9494d89432203527fcb22ac4def9b07c6532d 0.600000000000 1451182 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": 990862, "vin": [ { "gen": { "height": 990852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c8e6cdcba547034fafa18c425d9494d89432203527fcb22ac4def9b07c6532d" } } ], "extra": [ 1, 13, 161, 8, 38, 170, 131, 247, 164, 63, 25, 243, 164, 40, 233, 6, 188, 68, 0, 248, 89, 243, 79, 28, 162, 179, 102, 227, 87, 202, 36, 81, 88, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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