Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ceaba287dece0b22c74c3ac22df9c1127804aba7a46289467a2340f9489afe3

Tx prefix hash: 2bc390bd4a7f9d4754e302ea8a077fb5c9d4eca019804a97669b290d89123a95
Tx public key: 1b766ad0c4eb01e0c595f42792ccb10b73db0dc245f4108f50f662749ebcdfcb
Timestamp: 1745576195 Timestamp [UCT]: 2025-04-25 10:16:35 Age [y:d:h:m:s]: 00:016:06:57:51
Block: 1269085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11645 RingCT/type: yes/0
Extra: 011b766ad0c4eb01e0c595f42792ccb10b73db0dc245f4108f50f662749ebcdfcb021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5c252f9b42d72d09a37a1b8cb6f688dcfd76bce4a464e68ec2769ae5076356f 0.600000000000 1756320 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": 1269095, "vin": [ { "gen": { "height": 1269085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5c252f9b42d72d09a37a1b8cb6f688dcfd76bce4a464e68ec2769ae5076356f" } } ], "extra": [ 1, 27, 118, 106, 208, 196, 235, 1, 224, 197, 149, 244, 39, 146, 204, 177, 11, 115, 219, 13, 194, 69, 244, 16, 143, 80, 246, 98, 116, 158, 188, 223, 203, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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