Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82f6e02648a7927e67f3393d037463e9388e36b7856f557c8bba719b26b029c

Tx prefix hash: 0d2b7fcb22f1cc996509f55a6ab0f5f6a1bcbea5e263de9ba9fa407363abf897
Tx public key: e55ea06c19b9f2c23dd84136c3162236eb90f16c6df935197b6ace6450df05eb
Timestamp: 1761902069 Timestamp [UCT]: 2025-10-31 09:14:29 Age [y:d:h:m:s]: 00:008:22:28:12
Block: 1401838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6381 RingCT/type: yes/0
Extra: 01e55ea06c19b9f2c23dd84136c3162236eb90f16c6df935197b6ace6450df05eb02110000000c25a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc52e153a8f6e25ce82e383d52a96fc2bd5719c4f95480bdf02fe3e4e0d47ca3 0.600000000000 1890157 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": 1401848, "vin": [ { "gen": { "height": 1401838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc52e153a8f6e25ce82e383d52a96fc2bd5719c4f95480bdf02fe3e4e0d47ca3" } } ], "extra": [ 1, 229, 94, 160, 108, 25, 185, 242, 194, 61, 216, 65, 54, 195, 22, 34, 54, 235, 144, 241, 108, 109, 249, 53, 25, 123, 106, 206, 100, 80, 223, 5, 235, 2, 17, 0, 0, 0, 12, 37, 163, 90, 15, 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