Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15778c2880aa5f82c8845894c6bdbd4aa2555b66af14733ec0aab0f5461c4e5a

Tx prefix hash: 4f36997019273a0568f0c2d5cd19ef2f6072ecaf0757598391184d630aec8f37
Tx public key: 379f403b0c687701721babad4491183695adaef20e0b63d7c4f4a8d2408cd34b
Timestamp: 1704149294 Timestamp [UTC]: 2024-01-01 22:48:14 Age [y:d:h:m:s]: 02:135:06:08:19
Block: 926141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608743 RingCT/type: yes/0
Extra: 01379f403b0c687701721babad4491183695adaef20e0b63d7c4f4a8d2408cd34b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6948fa9d229f2882eeed4948c0928acb7d68a5ce454e3af7ca73d26acf274375 0.000600000000 1383915 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": 926151, "vin": [ { "gen": { "height": 926141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6948fa9d229f2882eeed4948c0928acb7d68a5ce454e3af7ca73d26acf274375" } } ], "extra": [ 1, 55, 159, 64, 59, 12, 104, 119, 1, 114, 27, 171, 173, 68, 145, 24, 54, 149, 173, 174, 242, 14, 11, 99, 215, 196, 244, 168, 210, 64, 140, 211, 75, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: