Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fedb5a931750c82a6d9b61d5fe211ddb487e538fd0712aed714c54ee056fc09e

Tx prefix hash: 9000ea1f505df007ea4f9dfe4a0cbb6a96bfcfd2637009d21a9a6587ffcb9152
Tx public key: cf0dc345914e7bea21cc1f3e8a846ab25ceac447a082b7cac3db83448c894c1c
Timestamp: 1738978442 Timestamp [UTC]: 2025-02-08 01:34:02 Age [y:d:h:m:s]: 01:283:18:58:43
Block: 1214463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466910 RingCT/type: yes/0
Extra: 01cf0dc345914e7bea21cc1f3e8a846ab25ceac447a082b7cac3db83448c894c1c021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e60b176840a0a7f1966a9692c4fcbbee67bca5d47b2917784aae518d63fb70eb 0.000600000000 1701254 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 dinastycoin-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": 1214473, "vin": [ { "gen": { "height": 1214463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e60b176840a0a7f1966a9692c4fcbbee67bca5d47b2917784aae518d63fb70eb" } } ], "extra": [ 1, 207, 13, 195, 69, 145, 78, 123, 234, 33, 204, 31, 62, 138, 132, 106, 178, 92, 234, 196, 71, 160, 130, 183, 202, 195, 219, 131, 68, 140, 137, 76, 28, 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): devel-2026-02-02-6303d2a (1.2) | monero version: