Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc9c4bda6853c9124a5e28ca5069b882e7248f28c96ce9b79de918ca415367e

Tx prefix hash: 17f616f5ea33d27c757ee39723dbce3042749fe936ef854f3db430e43fe4bb0d
Tx public key: 53783336cc6418af9b2c414a0c09bb6ddc1c9a007620b7b82817086800b4bd71
Timestamp: 1698337566 Timestamp [UCT]: 2023-10-26 16:26:06 Age [y:d:h:m:s]: 01:151:03:30:18
Block: 878187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369001 RingCT/type: yes/0
Extra: 0153783336cc6418af9b2c414a0c09bb6ddc1c9a007620b7b82817086800b4bd710211000000144b8f5122000000000000000000

1 output(s) for total of 0.755443400000 dcy

stealth address amount amount idx
00: d64dfb39e581c2e5e855d7d1015173537d36a275d33c18037fa78e0b8cad7af6 0.755443400000 1333611 of 0

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": 878197, "vin": [ { "gen": { "height": 878187 } } ], "vout": [ { "amount": 755443400, "target": { "key": "d64dfb39e581c2e5e855d7d1015173537d36a275d33c18037fa78e0b8cad7af6" } } ], "extra": [ 1, 83, 120, 51, 54, 204, 100, 24, 175, 155, 44, 65, 74, 12, 9, 187, 109, 220, 28, 154, 0, 118, 32, 183, 184, 40, 23, 8, 104, 0, 180, 189, 113, 2, 17, 0, 0, 0, 20, 75, 143, 81, 34, 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