Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e44f29dd2c5fc7190627cedb48ac0db71a5b3bebea8a2915ecf575a0987807

Tx prefix hash: 60e75ef478838a0573828521e27d1bcd20be2a8ee0b5ecdce75eb745c562b6ee
Tx public key: d2e19ee85b6a6b48b4bff41378c5efb19f1312e093236ba2c4e7b3f47ca536b8
Timestamp: 1756322616 Timestamp [UCT]: 2025-08-27 19:23:36 Age [y:d:h:m:s]: 00:128:16:27:34
Block: 1355768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91965 RingCT/type: yes/0
Extra: 01d2e19ee85b6a6b48b4bff41378c5efb19f1312e093236ba2c4e7b3f47ca536b80211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c47fa97b59134b259a6004872a45befa71665b6240e3a69f8ea0972a8497b6c9 0.600000000000 1843771 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": 1355778, "vin": [ { "gen": { "height": 1355768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c47fa97b59134b259a6004872a45befa71665b6240e3a69f8ea0972a8497b6c9" } } ], "extra": [ 1, 210, 225, 158, 232, 91, 106, 107, 72, 180, 191, 244, 19, 120, 197, 239, 177, 159, 19, 18, 224, 147, 35, 107, 162, 196, 231, 179, 244, 124, 165, 54, 184, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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