Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c74dc4e936c69fae2095f47b0c11e1e990898b3e91b5f080e2f5ab1ec8be8ab6

Tx prefix hash: 2c96836eb923020a667083719af8686ac2a07a15b308011b1a1972bb47bfc664
Tx public key: d94d4564a0dcad7a7a2b4fbe646fd063aaca340055f6d5cf2e00f531b4defacb
Timestamp: 1709020380 Timestamp [UCT]: 2024-02-27 07:53:00 Age [y:d:h:m:s]: 01:055:00:19:17
Block: 966536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300330 RingCT/type: yes/0
Extra: 01d94d4564a0dcad7a7a2b4fbe646fd063aaca340055f6d5cf2e00f531b4defacb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8cf8ef50e98041e3844a8fb4aedee1aef6a8bddf7cc387d14b2dacf465144f0 0.600000000000 1426297 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": 966546, "vin": [ { "gen": { "height": 966536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8cf8ef50e98041e3844a8fb4aedee1aef6a8bddf7cc387d14b2dacf465144f0" } } ], "extra": [ 1, 217, 77, 69, 100, 160, 220, 173, 122, 122, 43, 79, 190, 100, 111, 208, 99, 170, 202, 52, 0, 85, 246, 213, 207, 46, 0, 245, 49, 180, 222, 250, 203, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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