Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c871c2231f47258d5604d5b5c0e62993e5ff85415f347ca2b8cc01938554cf01

Tx prefix hash: 690209eb7aca8ef10826886c0f989f136f40f429f7c50d89c9e02c764b402835
Tx public key: 0bfff929eb787c47b388e2e166aef511d25724d326d8aba7fd7b57e0c521ddc8
Timestamp: 1705265102 Timestamp [UCT]: 2024-01-14 20:45:02 Age [y:d:h:m:s]: 01:063:11:05:54
Block: 935373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306459 RingCT/type: yes/0
Extra: 010bfff929eb787c47b388e2e166aef511d25724d326d8aba7fd7b57e0c521ddc802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9e8b0d93ca80eca174ba7704e3fb74f83edf89ad0a9985c7a020eb048966348 0.600000000000 1393389 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": 935383, "vin": [ { "gen": { "height": 935373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9e8b0d93ca80eca174ba7704e3fb74f83edf89ad0a9985c7a020eb048966348" } } ], "extra": [ 1, 11, 255, 249, 41, 235, 120, 124, 71, 179, 136, 226, 225, 102, 174, 245, 17, 210, 87, 36, 211, 38, 216, 171, 167, 253, 123, 87, 224, 197, 33, 221, 200, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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