Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291d476df57138a1e2aa0d9f39977ada817ccb10b0b82ca054c63b5ede7034e8

Tx prefix hash: bd9214a8d2fc9a142313becc8606575ce02d34492a2eefe1fe1e955bf1c9869c
Tx public key: 172c54c25c0ee916b074ad658ed49286593925baf70f0926912af0b1fed890b5
Timestamp: 1673900203 Timestamp [UCT]: 2023-01-16 20:16:43 Age [y:d:h:m:s]: 02:081:19:31:55
Block: 676225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580137 RingCT/type: yes/0
Extra: 01172c54c25c0ee916b074ad658ed49286593925baf70f0926912af0b1fed890b50211000000038b7b6602000000000000000000

1 output(s) for total of 3.526840414000 dcy

stealth address amount amount idx
00: a0ee07ff424afdc29ed00b67a5cb1ec93d3e72eae6f317adda9a26e4f531ee9b 3.526840414000 1117934 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": 676235, "vin": [ { "gen": { "height": 676225 } } ], "vout": [ { "amount": 3526840414, "target": { "key": "a0ee07ff424afdc29ed00b67a5cb1ec93d3e72eae6f317adda9a26e4f531ee9b" } } ], "extra": [ 1, 23, 44, 84, 194, 92, 14, 233, 22, 176, 116, 173, 101, 142, 212, 146, 134, 89, 57, 37, 186, 247, 15, 9, 38, 145, 42, 240, 177, 254, 216, 144, 181, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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