Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a604336e5c94944160f80e10336b6c69ca1dc1f4f84f96216477036fd45053d8

Tx prefix hash: 3b13c1879062dec53f3a746fb0f0ead8f9beb0644fd65f6920a19646a42dc393
Tx public key: d3dc646be6d89b82e1a5580de9e766a0e683935a9d289a47d6e0d5b4acf993fe
Timestamp: 1705600331 Timestamp [UCT]: 2024-01-18 17:52:11 Age [y:d:h:m:s]: 01:296:01:47:09
Block: 938156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470427 RingCT/type: yes/0
Extra: 01d3dc646be6d89b82e1a5580de9e766a0e683935a9d289a47d6e0d5b4acf993fe02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7e5dd3ff2653d0e84ee53a8f8350b288375f92fc2871c3e4d2a66b346fc294 0.600000000000 1396224 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": 938166, "vin": [ { "gen": { "height": 938156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7e5dd3ff2653d0e84ee53a8f8350b288375f92fc2871c3e4d2a66b346fc294" } } ], "extra": [ 1, 211, 220, 100, 107, 230, 216, 155, 130, 225, 165, 88, 13, 233, 231, 102, 160, 230, 131, 147, 90, 157, 40, 154, 71, 214, 224, 213, 180, 172, 249, 147, 254, 2, 17, 0, 0, 0, 8, 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