Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d3d02d568d961e8a9273df6a2e18b224516361663133f94d65fc10a860d477

Tx prefix hash: b102efce4728052084c1e50679a7b1b8fbb6bbb6dfd1f353e71a2804f37775b2
Tx public key: 4d7ec7c852c615eedf9c30c6b2aa1d25e22bb646bd8281a6967995a91547ff19
Timestamp: 1751448408 Timestamp [UCT]: 2025-07-02 09:26:48 Age [y:d:h:m:s]: 00:142:08:23:25
Block: 1317131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99973 RingCT/type: yes/0
Extra: 014d7ec7c852c615eedf9c30c6b2aa1d25e22bb646bd8281a6967995a91547ff1902110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca65324dc5844c026d771585095093d7e287b4c0dbf7e7305363de63f4c9a96e 0.600000000000 1804796 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": 1317141, "vin": [ { "gen": { "height": 1317131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca65324dc5844c026d771585095093d7e287b4c0dbf7e7305363de63f4c9a96e" } } ], "extra": [ 1, 77, 126, 199, 200, 82, 198, 21, 238, 223, 156, 48, 198, 178, 170, 29, 37, 226, 43, 182, 70, 189, 130, 129, 166, 150, 121, 149, 169, 21, 71, 255, 25, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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