Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 419a9f173be9d39602504ba797df97fac4a3a703f25a3a0b578ebcb5127cd290

Tx prefix hash: 871feaaf5f8f98becc77dd7922ca8a1cd95e216066897f59aef63d589041123a
Tx public key: 40d9a4e7b8873125c5c5b237bba0f9f17ef9f56eda955fad634da7add48f5fa3
Timestamp: 1752737305 Timestamp [UCT]: 2025-07-17 07:28:25 Age [y:d:h:m:s]: 00:170:21:01:32
Block: 1327254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120975 RingCT/type: yes/0
Extra: 0140d9a4e7b8873125c5c5b237bba0f9f17ef9f56eda955fad634da7add48f5fa3021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1020883c7366de9f2d33e4363c61e2dca9df6fe696e9c839bab327009811d066 0.600000000000 1815007 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": 1327264, "vin": [ { "gen": { "height": 1327254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1020883c7366de9f2d33e4363c61e2dca9df6fe696e9c839bab327009811d066" } } ], "extra": [ 1, 64, 217, 164, 231, 184, 135, 49, 37, 197, 197, 178, 55, 187, 160, 249, 241, 126, 249, 245, 110, 218, 149, 95, 173, 99, 77, 167, 173, 212, 143, 95, 163, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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