Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb444527c7c10588f451ca612aff74d64ac4f361167c9eeefe911a21c13016a6

Tx prefix hash: df6a120bb9f15642ad5e281eb3b38b088127ac6ac5b315b639d41b131ce9a952
Tx public key: 6af05436c8807d83d48a2e0f724c7a6cbeb55496bac4fa9bcb83491ac5f5622c
Timestamp: 1708072836 Timestamp [UCT]: 2024-02-16 08:40:36 Age [y:d:h:m:s]: 01:044:07:54:34
Block: 958664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292712 RingCT/type: yes/0
Extra: 016af05436c8807d83d48a2e0f724c7a6cbeb55496bac4fa9bcb83491ac5f5622c02110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32d5b06d16fbbb4d2afe1ff41feaa827789cb0c1f897b329301158b70d012557 0.600000000000 1418025 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": 958674, "vin": [ { "gen": { "height": 958664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32d5b06d16fbbb4d2afe1ff41feaa827789cb0c1f897b329301158b70d012557" } } ], "extra": [ 1, 106, 240, 84, 54, 200, 128, 125, 131, 212, 138, 46, 15, 114, 76, 122, 108, 190, 181, 84, 150, 186, 196, 250, 155, 203, 131, 73, 26, 197, 245, 98, 44, 2, 17, 0, 0, 0, 17, 89, 218, 211, 245, 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