Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4794f4bba5e6d274194e73db313cf1db9c6b9bb4ad1b4099ee9fa1dc7e30cd3a

Tx prefix hash: 8b62ffd807855a09acb7fca4106fb9b9683ac5782e8f6efad20fced179a78083
Tx public key: 5cc1b5e26eeb3be91df5a00801950f6fbbc2ad79c9150041413608a2e69084cf
Timestamp: 1708541762 Timestamp [UCT]: 2024-02-21 18:56:02 Age [y:d:h:m:s]: 00:324:13:23:57
Block: 962560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232343 RingCT/type: yes/0
Extra: 015cc1b5e26eeb3be91df5a00801950f6fbbc2ad79c9150041413608a2e69084cf02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f21efe782ce6a0f837082fa18617ca25db8f0334f8d5004a55887caf20581240 0.600000000000 1422201 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": 962570, "vin": [ { "gen": { "height": 962560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f21efe782ce6a0f837082fa18617ca25db8f0334f8d5004a55887caf20581240" } } ], "extra": [ 1, 92, 193, 181, 226, 110, 235, 59, 233, 29, 245, 160, 8, 1, 149, 15, 111, 187, 194, 173, 121, 201, 21, 0, 65, 65, 54, 8, 162, 230, 144, 132, 207, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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