Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c13bb1c783c6f401e068bc9969ee4a55ba45fea818394c6ab87df707f7db125

Tx prefix hash: 9a4f0c14471d067fcce980ff6899fb024ffb5b2ac1a69e3309812b5acb3b5b10
Tx public key: cac5c51727af4218b65ca59c332f0e20f814b401787ffc254f149174d06c70fb
Timestamp: 1749720784 Timestamp [UCT]: 2025-06-12 09:33:04 Age [y:d:h:m:s]: 00:162:04:36:27
Block: 1303363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113632 RingCT/type: yes/0
Extra: 01cac5c51727af4218b65ca59c332f0e20f814b401787ffc254f149174d06c70fb021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ef8e645663dfffef4535018b39dc0b39bf5f68bec2b244a8c443b81ea85de9 0.600000000000 1790942 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": 1303373, "vin": [ { "gen": { "height": 1303363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ef8e645663dfffef4535018b39dc0b39bf5f68bec2b244a8c443b81ea85de9" } } ], "extra": [ 1, 202, 197, 197, 23, 39, 175, 66, 24, 182, 92, 165, 156, 51, 47, 14, 32, 248, 20, 180, 1, 120, 127, 252, 37, 79, 20, 145, 116, 208, 108, 112, 251, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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