Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ceca40f1fa2c2c7391f3d6664df1304214cc8e9fcd5be2070ac1cb5ba219f43

Tx prefix hash: ec778343b08f474f823cbadc7feb770fe25774fd05fd7a7dc7f1dca6f25f43a6
Tx public key: 9e0890a7ba55c8e83f61df4d5cd55d7835b3c60f21e6f2cc112b09bb3b9b303c
Timestamp: 1710840580 Timestamp [UCT]: 2024-03-19 09:29:40 Age [y:d:h:m:s]: 01:290:20:13:12
Block: 981636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466630 RingCT/type: yes/0
Extra: 019e0890a7ba55c8e83f61df4d5cd55d7835b3c60f21e6f2cc112b09bb3b9b303c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d397606098668739b286fe697bb603ec74e88f53a9793da2b2b1ca0cb05ba843 0.600000000000 1441733 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": 981646, "vin": [ { "gen": { "height": 981636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d397606098668739b286fe697bb603ec74e88f53a9793da2b2b1ca0cb05ba843" } } ], "extra": [ 1, 158, 8, 144, 167, 186, 85, 200, 232, 63, 97, 223, 77, 92, 213, 93, 120, 53, 179, 198, 15, 33, 230, 242, 204, 17, 43, 9, 187, 59, 155, 48, 60, 2, 17, 0, 0, 0, 2, 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