Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b7d4e818ad6b19248476cc9f0b671acc39cf93586afb028890b0e7bb34a5e4b

Tx prefix hash: fc03b4aa877092787060c9fcd02cd477f6a6c420680147fa018ef75ed9a2c716
Tx public key: bed9cd152c5fe26444f04576edb805bd754455afc34a22a482b8f8bc91196231
Timestamp: 1784025986 Timestamp [UTC]: 2026-07-14 10:46:26 Age [y:d:h:m:s]: 00:127:06:34:31
Block: 1582058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 99215 RingCT/type: yes/0
Extra: 01bed9cd152c5fe26444f04576edb805bd754455afc34a22a482b8f8bc911962310208e4486a4fa706fbb2

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aad4cfc77bf040d04ae40572fd0d49e8064098d2deeac94e2fac826aadbe72a0 0.000600000000 2072052 of 15 <c1>

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": 1582068, "vin": [ { "gen": { "height": 1582058 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "aad4cfc77bf040d04ae40572fd0d49e8064098d2deeac94e2fac826aadbe72a0", "view_tag": "c1" } } } ], "extra": [ 1, 190, 217, 205, 21, 44, 95, 226, 100, 68, 240, 69, 118, 237, 184, 5, 189, 117, 68, 85, 175, 195, 74, 34, 164, 130, 184, 248, 188, 145, 25, 98, 49, 2, 8, 228, 72, 106, 79, 167, 6, 251, 178 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: