Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5591f4cd1d23009d9cfce444953427f0db9c977d79742e56b38df6b6d21f2b41

Tx prefix hash: bce034f7961a69b14e78754d393ce6dd052f138a513a9367dfa98a669d500796
Tx public key: e5fa3bf67954c1205b8aabf6b37b18e4c70948f87d6aaca60ab671d812844f87
Timestamp: 1745138208 Timestamp [UTC]: 2025-04-20 08:36:48 Age [y:d:h:m:s]: 01:213:05:45:39
Block: 1265447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416503 RingCT/type: yes/0
Extra: 01e5fa3bf67954c1205b8aabf6b37b18e4c70948f87d6aaca60ab671d812844f870211000000036c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfad64be6ecad6a31d000e46a79814e4457649cacb297d74518d8965f1c85dd1 0.000600000000 1752656 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": 1265457, "vin": [ { "gen": { "height": 1265447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfad64be6ecad6a31d000e46a79814e4457649cacb297d74518d8965f1c85dd1" } } ], "extra": [ 1, 229, 250, 59, 246, 121, 84, 193, 32, 91, 138, 171, 246, 179, 123, 24, 228, 199, 9, 72, 248, 125, 106, 172, 166, 10, 182, 113, 216, 18, 132, 79, 135, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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: