Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58d157f4cf07cd023995238a2f359d7ef8459d2b5384f1d5cbcae278ee4530c4

Tx prefix hash: 7314cf7f0e125bd31bea133c3d964ec6abd3767809057d25dd12e79ddb6dc137
Tx public key: 7818319960da70b0b6a010a54c44533a6a135832f30c04b1b96a3c73976202f6
Timestamp: 1743900700 Timestamp [UTC]: 2025-04-06 00:51:40 Age [y:d:h:m:s]: 01:226:17:32:17
Block: 1255201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426108 RingCT/type: yes/0
Extra: 017818319960da70b0b6a010a54c44533a6a135832f30c04b1b96a3c73976202f602110000000fdbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7b4e55327c2e57fd4a22e1b46821928c4898aafa1c91fc9296696b9223ad0d91 0.000600000000 1742304 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": 1255211, "vin": [ { "gen": { "height": 1255201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b4e55327c2e57fd4a22e1b46821928c4898aafa1c91fc9296696b9223ad0d91" } } ], "extra": [ 1, 120, 24, 49, 153, 96, 218, 112, 176, 182, 160, 16, 165, 76, 68, 83, 58, 106, 19, 88, 50, 243, 12, 4, 177, 185, 106, 60, 115, 151, 98, 2, 246, 2, 17, 0, 0, 0, 15, 219, 181, 113, 193, 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: