Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d71bdf255ceca44e0eb796c051f193f6a12e1863fc6a9e58b39eed348b68d3

Tx prefix hash: ec4779df02d8314ae052d294293d6849d87a5e546bb32193f2cb91dd7820baf7
Tx public key: 0444a042a68d37accd15b5ed62b0c8e442e982bfec4e62ef740db35ca55030e4
Timestamp: 1771574970 Timestamp [UTC]: 2026-02-20 08:09:30 Age [y:d:h:m:s]: 00:271:06:34:53
Block: 1481789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199403 RingCT/type: yes/0
Extra: 010444a042a68d37accd15b5ed62b0c8e442e982bfec4e62ef740db35ca55030e4021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7eac27167b119d8dcbdba4052b85441c53d552b448b45f46c948564f10148ec 0.000600000000 1971175 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": 1481799, "vin": [ { "gen": { "height": 1481789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7eac27167b119d8dcbdba4052b85441c53d552b448b45f46c948564f10148ec" } } ], "extra": [ 1, 4, 68, 160, 66, 166, 141, 55, 172, 205, 21, 181, 237, 98, 176, 200, 228, 66, 233, 130, 191, 236, 78, 98, 239, 116, 13, 179, 92, 165, 80, 48, 228, 2, 17, 0, 0, 0, 6, 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: