Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bafa74fea0cad7fdb8ae0bdb3b28012199aa69f3af10cee28f23210498b908b5

Tx prefix hash: 42ad2e27f181321398f80d02d94d0b090b9f2b7cc47a77d181f9904da6ae9ee7
Tx public key: edbd19e9d8eddeb06b8150837774c7c27c90fbe5067431cf59b7c0a5d2858cf2
Timestamp: 1702746244 Timestamp [UCT]: 2023-12-16 17:04:04 Age [y:d:h:m:s]: 01:026:09:58:41
Block: 914512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280226 RingCT/type: yes/0
Extra: 01edbd19e9d8eddeb06b8150837774c7c27c90fbe5067431cf59b7c0a5d2858cf2021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2adb3fcdbfb2f83b8bc2eaafb638f9986cbdbad64d92f605fbc64d849a62b4f0 0.600000000000 1371828 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": 914522, "vin": [ { "gen": { "height": 914512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2adb3fcdbfb2f83b8bc2eaafb638f9986cbdbad64d92f605fbc64d849a62b4f0" } } ], "extra": [ 1, 237, 189, 25, 233, 216, 237, 222, 176, 107, 129, 80, 131, 119, 116, 199, 194, 124, 144, 251, 229, 6, 116, 49, 207, 89, 183, 192, 165, 210, 133, 140, 242, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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