Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8128a8ec980fb2bd9f1e21204897785c5ff863ce68d19c02a6a199d99ff5289a

Tx prefix hash: 0af741ecc04b062c2c4fd343494a3d860377b9f42f3afe6cdbb6652122148362
Tx public key: 720262648191e0ec68ebf8b1aeff7b7cf36c669c6c733145ab7fe5a401fb20e2
Timestamp: 1744651841 Timestamp [UTC]: 2025-04-14 17:30:41 Age [y:d:h:m:s]: 01:221:14:22:43
Block: 1261429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422065 RingCT/type: yes/0
Extra: 01720262648191e0ec68ebf8b1aeff7b7cf36c669c6c733145ab7fe5a401fb20e20211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 338d34f137ac7652fa6b50140135937019ea45494f2ce8bb2f484eb99854a2df 0.000600000000 1748598 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": 1261439, "vin": [ { "gen": { "height": 1261429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338d34f137ac7652fa6b50140135937019ea45494f2ce8bb2f484eb99854a2df" } } ], "extra": [ 1, 114, 2, 98, 100, 129, 145, 224, 236, 104, 235, 248, 177, 174, 255, 123, 124, 243, 108, 102, 156, 108, 115, 49, 69, 171, 127, 229, 164, 1, 251, 32, 226, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: