Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfc485a91092df4a37dbbe5ce1d35dfba3afc4133845e5c9f456694d8a2744e9

Tx prefix hash: bdf0bef1472619bfe7a3813846e0c05a8465e182b132d001e407fd20e8538780
Tx public key: 5dd80af0ac56a0f7462aef403fa74998e58ff812e657b20eae219e4af6bb53cd
Timestamp: 1774027451 Timestamp [UTC]: 2026-03-20 17:24:11 Age [y:d:h:m:s]: 00:240:03:07:35
Block: 1502058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177086 RingCT/type: yes/0
Extra: 015dd80af0ac56a0f7462aef403fa74998e58ff812e657b20eae219e4af6bb53cd021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e5ae789aa21eab6489197653ce48701c82db86920f628059314e13ca8f63c729 0.000600000000 1991752 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": 1502068, "vin": [ { "gen": { "height": 1502058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ae789aa21eab6489197653ce48701c82db86920f628059314e13ca8f63c729" } } ], "extra": [ 1, 93, 216, 10, 240, 172, 86, 160, 247, 70, 42, 239, 64, 63, 167, 73, 152, 229, 143, 248, 18, 230, 87, 178, 14, 174, 33, 158, 74, 246, 187, 83, 205, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: