Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 005cbc8dba68c566c5fc40c15e83ccfc4c072d77e0f6d43e9e0f94541a673ee5

Tx prefix hash: 8b554e651de2694fdbd9c9d08d35485b9256ddf6a6ceec43fafff4daba6a93fd
Tx public key: 589a25c64adf94b674cbf81245c2eeda4d02ffc91d4c235a25790c171285b39a
Timestamp: 1750503235 Timestamp [UTC]: 2025-06-21 10:53:55 Age [y:d:h:m:s]: 01:150:05:22:02
Block: 1309707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371529 RingCT/type: yes/0
Extra: 01589a25c64adf94b674cbf81245c2eeda4d02ffc91d4c235a25790c171285b39a02110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bab53f87a11661f195363677ea79bab9fb85571dea56bb5eb4a7603b6b98d3f8 0.000600000000 1797324 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": 1309717, "vin": [ { "gen": { "height": 1309707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bab53f87a11661f195363677ea79bab9fb85571dea56bb5eb4a7603b6b98d3f8" } } ], "extra": [ 1, 88, 154, 37, 198, 74, 223, 148, 182, 116, 203, 248, 18, 69, 194, 238, 218, 77, 2, 255, 201, 29, 76, 35, 90, 37, 121, 12, 23, 18, 133, 179, 154, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: