Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e15c98efee45b468a538f996f20fe58bd6be21aac0907d7180055f4d5118640

Tx prefix hash: 68e684215ad60cde6020d7e362f205fe3a0d8dc9d378e908f7617412effd412d
Tx public key: 6e4a00e0358c49484e742b5fe7a7f0d3500eb329f6021feed0856c21eb599ee8
Timestamp: 1742982240 Timestamp [UTC]: 2025-03-26 09:44:00 Age [y:d:h:m:s]: 01:238:15:44:10
Block: 1247598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434701 RingCT/type: yes/0
Extra: 016e4a00e0358c49484e742b5fe7a7f0d3500eb329f6021feed0856c21eb599ee8021100000002165b77a1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f67a6b00fd639dbfbb2804230c95e5aa8914b55113605f17a206230d32e13d8a 0.000600000000 1734621 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": 1247608, "vin": [ { "gen": { "height": 1247598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f67a6b00fd639dbfbb2804230c95e5aa8914b55113605f17a206230d32e13d8a" } } ], "extra": [ 1, 110, 74, 0, 224, 53, 140, 73, 72, 78, 116, 43, 95, 231, 167, 240, 211, 80, 14, 179, 41, 246, 2, 31, 238, 208, 133, 108, 33, 235, 89, 158, 232, 2, 17, 0, 0, 0, 2, 22, 91, 119, 161, 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: