Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52563d44ca5d3cfa47bab059e0a385f744488d75f9de4c8fc30163e667aa579

Tx prefix hash: ed249691c56c1cebf524354ebc15f6a1782da1bf0a10ed164a7c4987dfa9942b
Tx public key: 0d9ff9c7e382cc30cd08e70f597a572b39b46caa3ae5e248acd24bde76dba57a
Timestamp: 1713033651 Timestamp [UCT]: 2024-04-13 18:40:51 Age [y:d:h:m:s]: 00:317:23:35:36
Block: 999773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227333 RingCT/type: yes/0
Extra: 010d9ff9c7e382cc30cd08e70f597a572b39b46caa3ae5e248acd24bde76dba57a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a94074c067d157c8415b08c4293959c5ff6d37dc2e4b37cf7cead1c2c6bb8c 0.600000000000 1460255 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": 999783, "vin": [ { "gen": { "height": 999773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a94074c067d157c8415b08c4293959c5ff6d37dc2e4b37cf7cead1c2c6bb8c" } } ], "extra": [ 1, 13, 159, 249, 199, 227, 130, 204, 48, 205, 8, 231, 15, 89, 122, 87, 43, 57, 180, 108, 170, 58, 229, 226, 72, 172, 210, 75, 222, 118, 219, 165, 122, 2, 17, 0, 0, 0, 2, 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