Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27796a5bf0b18a411ecc2086ead50082eb986dce8efcafeb39bf58059c7e459c

Tx prefix hash: 724eb1588970e54872b8ee75f8db0ded80c5659baa36ae7dc5c6e4c12a8ecdb7
Tx public key: 80f94891a9b4e8e3eda434427b9526e04f6ad39538f063aa32c892f6b28dd0e0
Timestamp: 1742302116 Timestamp [UCT]: 2025-03-18 12:48:36 Age [y:d:h:m:s]: 00:294:08:57:20
Block: 1241991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208180 RingCT/type: yes/0
Extra: 0180f94891a9b4e8e3eda434427b9526e04f6ad39538f063aa32c892f6b28dd0e00211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d20ef3c51fc0ef1766487e0ce90d77194af25ec5fb26e6c1d2d93d7be854aaa2 0.600000000000 1728964 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": 1242001, "vin": [ { "gen": { "height": 1241991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d20ef3c51fc0ef1766487e0ce90d77194af25ec5fb26e6c1d2d93d7be854aaa2" } } ], "extra": [ 1, 128, 249, 72, 145, 169, 180, 232, 227, 237, 164, 52, 66, 123, 149, 38, 224, 79, 106, 211, 149, 56, 240, 99, 170, 50, 200, 146, 246, 178, 141, 208, 224, 2, 17, 0, 0, 0, 16, 31, 10, 83, 235, 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