Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 666ff6060109ab6c7bae0dfd80d17eceae9e3bdc8cf69f4dde6edf025df6b3f0

Tx prefix hash: d314f5d82bc3dd921aa508f84e8a10434e09d5f03c59cbaa1fc7d56bfa13250b
Tx public key: 093a72d0db41269bc00d9f55237f3011908d08569be580ff6f4a9a23011f2ebf
Timestamp: 1743385631 Timestamp [UTC]: 2025-03-31 01:47:11 Age [y:d:h:m:s]: 00:360:12:40:02
Block: 1250936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255337 RingCT/type: yes/0
Extra: 01093a72d0db41269bc00d9f55237f3011908d08569be580ff6f4a9a23011f2ebf0211000000081a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ba56671f68a0575f1aa24f59df293be08b856d2b0de0268d4a90433f656b21f 0.000600000000 1737995 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": 1250946, "vin": [ { "gen": { "height": 1250936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ba56671f68a0575f1aa24f59df293be08b856d2b0de0268d4a90433f656b21f" } } ], "extra": [ 1, 9, 58, 114, 208, 219, 65, 38, 155, 192, 13, 159, 85, 35, 127, 48, 17, 144, 141, 8, 86, 155, 229, 128, 255, 111, 74, 154, 35, 1, 31, 46, 191, 2, 17, 0, 0, 0, 8, 26, 151, 4, 3, 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) | dinastycoin version: tesla-369