Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60d714c90437228398cf3baa943a54ff5f0247e74c1bb1eb2e1098a502f3c17c

Tx prefix hash: 999979a97fdde50a4787367b003014109c435c04bf57f3f7044955e571a8f216
Tx public key: a4e3c4310e359ecb8194ba23f2f5d69ea52c915fb68dbd1ab1bbad473c5e399a
Timestamp: 1754856281 Timestamp [UCT]: 2025-08-10 20:04:41 Age [y:d:h:m:s]: 00:004:22:29:00
Block: 1344346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3027 RingCT/type: yes/0
Extra: 01a4e3c4310e359ecb8194ba23f2f5d69ea52c915fb68dbd1ab1bbad473c5e399a021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16171f176925918bb32382f6952f73b8733d2e8a8c749af6d874d2178f799772 0.600000000000 1832229 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": 1344356, "vin": [ { "gen": { "height": 1344346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16171f176925918bb32382f6952f73b8733d2e8a8c749af6d874d2178f799772" } } ], "extra": [ 1, 164, 227, 196, 49, 14, 53, 158, 203, 129, 148, 186, 35, 242, 245, 214, 158, 165, 44, 145, 95, 182, 141, 189, 26, 177, 187, 173, 71, 60, 94, 57, 154, 2, 17, 0, 0, 0, 2, 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