Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2209d7c4bac059bf7473d8542361005cf806815476f27d6694e8a9b3dd7cd7c3

Tx prefix hash: 973f874fa6d53e9e331e8a3936d7b5a01503dd33ca3c81e6d9b00d0e8f03b7e2
Tx public key: 417f6126237d96922d78899e0b0ba5abab02b41df2c58332c946a35067adca3d
Timestamp: 1764418795 Timestamp [UCT]: 2025-11-29 12:19:55 Age [y:d:h:m:s]: 00:062:16:56:50
Block: 1422685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44706 RingCT/type: yes/0
Extra: 01417f6126237d96922d78899e0b0ba5abab02b41df2c58332c946a35067adca3d021100000002da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d87ee462d87573c91a087b0964134b065fbf187e89e7ce2aa2e6852ddcdcde06 0.600000000000 1911258 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": 1422695, "vin": [ { "gen": { "height": 1422685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d87ee462d87573c91a087b0964134b065fbf187e89e7ce2aa2e6852ddcdcde06" } } ], "extra": [ 1, 65, 127, 97, 38, 35, 125, 150, 146, 45, 120, 137, 158, 11, 11, 165, 171, 171, 2, 180, 29, 242, 197, 131, 50, 201, 70, 163, 80, 103, 173, 202, 61, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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