Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80dcbcff4649eb2f9809aaa0306b19882f16b8c7a0079c3ac4d8f2edeccf4b77

Tx prefix hash: 150778cd3593b574e7256679f4ad39490f2bd1b60921596307dab2a2df9d1cd3
Tx public key: 1cfc8d4289a8e42716d84bea4d756a004f7d6f0b98f090e2b6e7a705a9eb2702
Timestamp: 1758477541 Timestamp [UCT]: 2025-09-21 17:59:01 Age [y:d:h:m:s]: 00:105:07:33:24
Block: 1373441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75415 RingCT/type: yes/0
Extra: 011cfc8d4289a8e42716d84bea4d756a004f7d6f0b98f090e2b6e7a705a9eb2702021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d09369f4f467af78d87042b353b57168a8c9a069e8fec26cea0205a9eb34d2 0.600000000000 1861526 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": 1373451, "vin": [ { "gen": { "height": 1373441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d09369f4f467af78d87042b353b57168a8c9a069e8fec26cea0205a9eb34d2" } } ], "extra": [ 1, 28, 252, 141, 66, 137, 168, 228, 39, 22, 216, 75, 234, 77, 117, 106, 0, 79, 125, 111, 11, 152, 240, 144, 226, 182, 231, 167, 5, 169, 235, 39, 2, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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