Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75a4fe7293cc71ba46bb19d7b3c1129669f1b47e73790d6a586634b454cb2e5

Tx prefix hash: 4e09e4eba3fda9e1fb955d824a93afb2bd0221befaa2a72f029d3128d405d0b2
Tx public key: df0c08176efab34b7d269d96ad1d5cee5cd70cbc80270a2c43cb7a661e514e74
Timestamp: 1739713779 Timestamp [UCT]: 2025-02-16 13:49:39 Age [y:d:h:m:s]: 00:350:14:55:25
Block: 1220519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248290 RingCT/type: yes/0
Extra: 01df0c08176efab34b7d269d96ad1d5cee5cd70cbc80270a2c43cb7a661e514e74021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40a61d01bbd658fe4792de947fc60c735f6cd4685f3367ffe680256f1c842207 0.600000000000 1707360 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": 1220529, "vin": [ { "gen": { "height": 1220519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40a61d01bbd658fe4792de947fc60c735f6cd4685f3367ffe680256f1c842207" } } ], "extra": [ 1, 223, 12, 8, 23, 110, 250, 179, 75, 125, 38, 157, 150, 173, 29, 92, 238, 92, 215, 12, 188, 128, 39, 10, 44, 67, 203, 122, 102, 30, 81, 78, 116, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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