Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eb06ea345920238d909b1ccb8f74ff4b8300de7988894ea2789ea3e24c3b87d

Tx prefix hash: 558fa51622e9898fcfd82f7140751ea828376eeb28a999d47a7d4b5000002d7b
Tx public key: b00478aa0929c63ba92d7cae41fd70421a4d1a93156b6f850b6bdd1bc98c0a64
Timestamp: 1738600497 Timestamp [UCT]: 2025-02-03 16:34:57 Age [y:d:h:m:s]: 00:290:05:17:03
Block: 1211315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205199 RingCT/type: yes/0
Extra: 01b00478aa0929c63ba92d7cae41fd70421a4d1a93156b6f850b6bdd1bc98c0a64021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e2a6dc0dad85569844356dac8bf34f60e7edf700563b3b1454c493a132f4471 0.600000000000 1698076 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": 1211325, "vin": [ { "gen": { "height": 1211315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2a6dc0dad85569844356dac8bf34f60e7edf700563b3b1454c493a132f4471" } } ], "extra": [ 1, 176, 4, 120, 170, 9, 41, 198, 59, 169, 45, 124, 174, 65, 253, 112, 66, 26, 77, 26, 147, 21, 107, 111, 133, 11, 107, 221, 27, 201, 140, 10, 100, 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