Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9e39342a415807d46b25078bcf5595b40243809ad911a0afd33504a48c7d7e

Tx prefix hash: 330f7f8ce78de4d99c8afce7877fb56d586ead46ec5a225d6f21436dc15c8e1f
Tx public key: 6da778dc8f2480512c6aa5c0984d79ec32b79020a69c2956ee5d330c7fbb605c
Timestamp: 1734075558 Timestamp [UCT]: 2024-12-13 07:39:18 Age [y:d:h:m:s]: 00:097:22:55:47
Block: 1174166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69782 RingCT/type: yes/0
Extra: 016da778dc8f2480512c6aa5c0984d79ec32b79020a69c2956ee5d330c7fbb605c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a8d538f6e333b1ccea1505ce64db570cfba83d5f2141593825527d64fabf6e 0.600000000000 1660283 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": 1174176, "vin": [ { "gen": { "height": 1174166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a8d538f6e333b1ccea1505ce64db570cfba83d5f2141593825527d64fabf6e" } } ], "extra": [ 1, 109, 167, 120, 220, 143, 36, 128, 81, 44, 106, 165, 192, 152, 77, 121, 236, 50, 183, 144, 32, 166, 156, 41, 86, 238, 93, 51, 12, 127, 187, 96, 92, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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