Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b86fa6741a5d8eed955a1a62709dccddc1278937864437ef02821ed2bfefeb4

Tx prefix hash: 12ccc91d8dbdadd18474a0ba364ef90319dd6ded4fc37dc69e1035267eaabd4b
Tx public key: fe4d992a9f08b7c271924a716f321b4ede461fd75f5e9f17168342945ae0364b
Timestamp: 1741244765 Timestamp [UTC]: 2025-03-06 07:06:05 Age [y:d:h:m:s]: 01:068:03:46:41
Block: 1233223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299574 RingCT/type: yes/0
Extra: 01fe4d992a9f08b7c271924a716f321b4ede461fd75f5e9f17168342945ae0364b021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad63145bd0e2936e0f4bb52a3e384320c9a9d20a894bbd34a9ec940eb5c60712 0.000600000000 1720142 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": 1233233, "vin": [ { "gen": { "height": 1233223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad63145bd0e2936e0f4bb52a3e384320c9a9d20a894bbd34a9ec940eb5c60712" } } ], "extra": [ 1, 254, 77, 153, 42, 159, 8, 183, 194, 113, 146, 74, 113, 111, 50, 27, 78, 222, 70, 31, 215, 95, 94, 159, 23, 22, 131, 66, 148, 90, 224, 54, 75, 2, 17, 0, 0, 0, 4, 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: