Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5caefea4bceb794ee59444b4bed64c34d3699f599b1f85bedeac15829ae40ba

Tx prefix hash: 349536d10f1b79c97af08e6fd05d66ac942e59791cc3dcb8f5eaaf77abd3efa9
Tx public key: c1e9418c63f3c7f23f7e45e79fb4e6e71b359c8ea9634155d4d63a937b3cb920
Timestamp: 1745658285 Timestamp [UCT]: 2025-04-26 09:04:45 Age [y:d:h:m:s]: 00:198:12:33:58
Block: 1269765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139586 RingCT/type: yes/0
Extra: 01c1e9418c63f3c7f23f7e45e79fb4e6e71b359c8ea9634155d4d63a937b3cb9200211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cddbe3fe13d9ce7d4a67d1e590b7d11a7596a38f5b92f81d2c8e379c46657855 0.600000000000 1757004 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": 1269775, "vin": [ { "gen": { "height": 1269765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cddbe3fe13d9ce7d4a67d1e590b7d11a7596a38f5b92f81d2c8e379c46657855" } } ], "extra": [ 1, 193, 233, 65, 140, 99, 243, 199, 242, 63, 126, 69, 231, 159, 180, 230, 231, 27, 53, 156, 142, 169, 99, 65, 85, 212, 214, 58, 147, 123, 60, 185, 32, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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