Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fef7e4b6918cc07afa9594cae10b94722b814bddeced720f4928c53735b856a

Tx prefix hash: 047b1ded0302ad41fceab8db7376c83147cb242a39e3caeeca6ff7e24632dc07
Tx public key: cdf400b08a2b3928b856ef3c8d10f345a2a15d48d75a70511da94b35e010dd81
Timestamp: 1771366129 Timestamp [UTC]: 2026-02-17 22:08:49 Age [y:d:h:m:s]: 00:089:13:11:43
Block: 1480041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56576 RingCT/type: yes/0
Extra: 01cdf400b08a2b3928b856ef3c8d10f345a2a15d48d75a70511da94b35e010dd81021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f3e0e7359c327cc6be897643c4e6442043bf0f6078bcd14c1331e89b989c273 0.000600000000 1969405 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": 1480051, "vin": [ { "gen": { "height": 1480041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f3e0e7359c327cc6be897643c4e6442043bf0f6078bcd14c1331e89b989c273" } } ], "extra": [ 1, 205, 244, 0, 176, 138, 43, 57, 40, 184, 86, 239, 60, 141, 16, 243, 69, 162, 161, 93, 72, 215, 90, 112, 81, 29, 169, 75, 53, 224, 16, 221, 129, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: