Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd44f77a6277d967fc35309126436665f96ea9d368cc263b66aaf6fa7723deac

Tx prefix hash: 3c1c2daf9e0633a09ead4e424d72dd8ac10d82d75484a13d0165d5738861e55c
Tx public key: 1ffef6ce5810f391859ffb0ea6c99ca7a0398c596481f43105e7f30f8efedb61
Timestamp: 1743084305 Timestamp [UTC]: 2025-03-27 14:05:05 Age [y:d:h:m:s]: 01:150:21:16:04
Block: 1248438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372210 RingCT/type: yes/0
Extra: 011ffef6ce5810f391859ffb0ea6c99ca7a0398c596481f43105e7f30f8efedb61021100000004165b77a1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f91db3df36d0d676509470231a81a1d4de49360fdc6789370c18427f2bb5cfa1 0.000600000000 1735467 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": 1248448, "vin": [ { "gen": { "height": 1248438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f91db3df36d0d676509470231a81a1d4de49360fdc6789370c18427f2bb5cfa1" } } ], "extra": [ 1, 31, 254, 246, 206, 88, 16, 243, 145, 133, 159, 251, 14, 166, 201, 156, 167, 160, 57, 140, 89, 100, 129, 244, 49, 5, 231, 243, 15, 142, 254, 219, 97, 2, 17, 0, 0, 0, 4, 22, 91, 119, 161, 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: