Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d73b60f43efe11529ca27e49bfa1c5ab7a4fece05213c1854cd7442ed00cf4d0

Tx prefix hash: 944250f653bf16c180bf0af87830931cbf3553493871b8adbed7a8a9f8de39c0
Tx public key: 3048375f319f264ab7d52843c6ed8fc1f9cc51f39fa6a822c4191a80568ef5ca
Timestamp: 1771478808 Timestamp [UTC]: 2026-02-19 05:26:48 Age [y:d:h:m:s]: 00:271:23:14:41
Block: 1480994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199895 RingCT/type: yes/0
Extra: 013048375f319f264ab7d52843c6ed8fc1f9cc51f39fa6a822c4191a80568ef5ca021100000014e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea664a0aabe904d122f72b04305eb7c1568214d573b59d2869d3e9d58e3f00a3 0.000600000000 1970368 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": 1481004, "vin": [ { "gen": { "height": 1480994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea664a0aabe904d122f72b04305eb7c1568214d573b59d2869d3e9d58e3f00a3" } } ], "extra": [ 1, 48, 72, 55, 95, 49, 159, 38, 74, 183, 213, 40, 67, 198, 237, 143, 193, 249, 204, 81, 243, 159, 166, 168, 34, 196, 25, 26, 128, 86, 142, 245, 202, 2, 17, 0, 0, 0, 20, 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: