Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbf53edff9f7f5e930073a216a3976a46f2315975d62d9e577fc2b67a22dcf0

Tx prefix hash: dd316cce46330077fe9a96752ae3a5fec12f4aa374272d760c0a7f14f91675c0
Tx public key: eeb1e4f8b157cb034228f1701cb7bddd6d18f3e38072a438672a0ad89da28bfb
Timestamp: 1712880214 Timestamp [UCT]: 2024-04-12 00:03:34 Age [y:d:h:m:s]: 01:035:07:03:55
Block: 998505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286224 RingCT/type: yes/0
Extra: 01eeb1e4f8b157cb034228f1701cb7bddd6d18f3e38072a438672a0ad89da28bfb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d6035fe607753d490c58928b31528c949fe42e7d5e1bac57ea08750bc6fece0 0.600000000000 1458957 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": 998515, "vin": [ { "gen": { "height": 998505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d6035fe607753d490c58928b31528c949fe42e7d5e1bac57ea08750bc6fece0" } } ], "extra": [ 1, 238, 177, 228, 248, 177, 87, 203, 3, 66, 40, 241, 112, 28, 183, 189, 221, 109, 24, 243, 227, 128, 114, 164, 56, 103, 42, 10, 216, 157, 162, 139, 251, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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