Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d41b9702c5df75bac278c0a8a6f080f7ed9a5c66148432d09ecd1826772abf5

Tx prefix hash: bd3248c0d11b6507937d8ac6faa41918c073875a24003559bd90d4f782f6793e
Tx public key: b7a5774ac05765ecfd59ec659c7ac9eedd4954f2c7bef9a657135ca9ff197dc2
Timestamp: 1712515240 Timestamp [UCT]: 2024-04-07 18:40:40 Age [y:d:h:m:s]: 01:037:21:49:03
Block: 995474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288097 RingCT/type: yes/0
Extra: 01b7a5774ac05765ecfd59ec659c7ac9eedd4954f2c7bef9a657135ca9ff197dc202110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa89f58ea2bfeb0df4e5dc718f8c6263d5a5e447835f4176f05fc34fb66eb377 0.600000000000 1455884 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": 995484, "vin": [ { "gen": { "height": 995474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa89f58ea2bfeb0df4e5dc718f8c6263d5a5e447835f4176f05fc34fb66eb377" } } ], "extra": [ 1, 183, 165, 119, 74, 192, 87, 101, 236, 253, 89, 236, 101, 156, 122, 201, 238, 221, 73, 84, 242, 199, 190, 249, 166, 87, 19, 92, 169, 255, 25, 125, 194, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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