Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 122700c78844bea384e4d68e20ff40ae02b772b90eb8adfb51ea1dd48b6b4b8d

Tx prefix hash: 79a7eda9498c979eeaf521b81515db68c535165023d770f7f5e074ab1ac34199
Tx public key: f8b4c3a4d0b6169e4c739644581ff0129305ffe2488f2e74c5ad7ffa68698b24
Timestamp: 1732732786 Timestamp [UCT]: 2024-11-27 18:39:46 Age [y:d:h:m:s]: 00:154:00:38:50
Block: 1163022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109894 RingCT/type: yes/0
Extra: 01f8b4c3a4d0b6169e4c739644581ff0129305ffe2488f2e74c5ad7ffa68698b240211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf91faffdc1ce6c320daa32fa0e8fd13b7967ce2e4c9adea2aea7def4e21bcb8 0.600000000000 1648685 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": 1163032, "vin": [ { "gen": { "height": 1163022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf91faffdc1ce6c320daa32fa0e8fd13b7967ce2e4c9adea2aea7def4e21bcb8" } } ], "extra": [ 1, 248, 180, 195, 164, 208, 182, 22, 158, 76, 115, 150, 68, 88, 31, 240, 18, 147, 5, 255, 226, 72, 143, 46, 116, 197, 173, 127, 250, 104, 105, 139, 36, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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