Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a291c6b29e731122f19e03ca6c07715ba125be38175f6b86f551c6c9a7de270a

Tx prefix hash: bd7879cf514b28d6b5044c3bb3a73546c1e71df27bc679d0fdf760a3e1ef9527
Tx public key: 1f94ecdd120204d0bfd802ecfd99a7fdb51dad514c5c41238ca651da572e85c8
Timestamp: 1726101156 Timestamp [UCT]: 2024-09-12 00:32:36 Age [y:d:h:m:s]: 00:064:02:42:01
Block: 1108137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45824 RingCT/type: yes/0
Extra: 011f94ecdd120204d0bfd802ecfd99a7fdb51dad514c5c41238ca651da572e85c8021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cdeb8b862680b35de48be1a0225ea2b7d3b7fecb4ecb5315e0fec0714921ae8 0.600000000000 1585928 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": 1108147, "vin": [ { "gen": { "height": 1108137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cdeb8b862680b35de48be1a0225ea2b7d3b7fecb4ecb5315e0fec0714921ae8" } } ], "extra": [ 1, 31, 148, 236, 221, 18, 2, 4, 208, 191, 216, 2, 236, 253, 153, 167, 253, 181, 29, 173, 81, 76, 92, 65, 35, 140, 166, 81, 218, 87, 46, 133, 200, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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