Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c2e8449d229e0f58daa182fc06242b3f800e130289b96aa180b57c171f0c46

Tx prefix hash: b5ad708eb8fd776b1e293b8f09458452758943ece5e42f6fea1560bee797bc44
Tx public key: a4ace24ab6a0faf6221269d18d302dc31b950986eaafaff80e0d8814cab8e1fa
Timestamp: 1724691835 Timestamp [UCT]: 2024-08-26 17:03:55 Age [y:d:h:m:s]: 00:294:19:59:14
Block: 1096445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210526 RingCT/type: yes/0
Extra: 01a4ace24ab6a0faf6221269d18d302dc31b950986eaafaff80e0d8814cab8e1fa021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7a4ceb624688bdd08934a17c22b60ddee451afdaf2ff91031d3b18c7e096e30 0.600000000000 1571634 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": 1096455, "vin": [ { "gen": { "height": 1096445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7a4ceb624688bdd08934a17c22b60ddee451afdaf2ff91031d3b18c7e096e30" } } ], "extra": [ 1, 164, 172, 226, 74, 182, 160, 250, 246, 34, 18, 105, 209, 141, 48, 45, 195, 27, 149, 9, 134, 234, 175, 175, 248, 14, 13, 136, 20, 202, 184, 225, 250, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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