Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 317f5de72e1e76d6410377fceeccde71ef37c379d9a599ef1730da54c6a643d2

Tx prefix hash: d24ab2e9dec86a9ed1ff5035106ff3e98f53415a3b6918ec5cdf009c87c0fef9
Tx public key: 09441e5c1027deedcaa14ca672f6c9dc4c2003a7f8a504a248b528cb3a1e8802
Timestamp: 1793347470 Timestamp [UTC]: 2026-10-30 08:04:30 Age [y:d:h:m:s]: 00:023:09:21:32
Block: 1665954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 17540 RingCT/type: yes/0
Extra: 0109441e5c1027deedcaa14ca672f6c9dc4c2003a7f8a504a248b528cb3a1e8802

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f42ffed421245add13a34fb272f7ddb115a62f0565ada75ddf8961aaa777ea29 0.000600000000 2156712 of 15 <17>

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": 1665964, "vin": [ { "gen": { "height": 1665954 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f42ffed421245add13a34fb272f7ddb115a62f0565ada75ddf8961aaa777ea29", "view_tag": "17" } } } ], "extra": [ 1, 9, 68, 30, 92, 16, 39, 222, 237, 202, 161, 76, 166, 114, 246, 201, 220, 76, 32, 3, 167, 248, 165, 4, 162, 72, 181, 40, 203, 58, 30, 136, 2 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: