Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f23711da97e028cccefa954636158fda6c12c0c96a9efd3d1d5d7096e1d67d

Tx prefix hash: ab3786328cfa61b2167cb14f2ff58c50f0d1fcb456a16906fb1422f38453080e
Tx public key: 408c46a0ee127b738e9391615e25df894b098be1766b252362cd152c89eef747
Timestamp: 1687596052 Timestamp [UCT]: 2023-06-24 08:40:52 Age [y:d:h:m:s]: 01:248:22:35:55
Block: 789169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439030 RingCT/type: yes/0
Extra: 01408c46a0ee127b738e9391615e25df894b098be1766b252362cd152c89eef74702110000000475e3f0e9000000000000000000

1 output(s) for total of 1.489894953000 dcy

stealth address amount amount idx
00: 286d65a456b6a4c0959e8c05b53e5e81b75015a9f6318258e4319abc54f250f3 1.489894953000 1239366 of 0

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": 789179, "vin": [ { "gen": { "height": 789169 } } ], "vout": [ { "amount": 1489894953, "target": { "key": "286d65a456b6a4c0959e8c05b53e5e81b75015a9f6318258e4319abc54f250f3" } } ], "extra": [ 1, 64, 140, 70, 160, 238, 18, 123, 115, 142, 147, 145, 97, 94, 37, 223, 137, 75, 9, 139, 225, 118, 107, 37, 35, 98, 205, 21, 44, 137, 238, 247, 71, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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