Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ff30ce36a4f558d6f0f5a0826291e9bd0b37689ec2fe8b685aa482bede3dc7e

Tx prefix hash: 6ab7725048ee71fd0dfba5f3cd4af2a976cdd6f750fd8200ba9425e858fe4ca3
Tx public key: 7a8e6dad88e39b3c876af8b0e93792a73be01eb19a3eff4d3cb519a44bb82f76
Timestamp: 1756353803 Timestamp [UTC]: 2025-08-28 04:03:23 Age [y:d:h:m:s]: 01:084:18:11:36
Block: 1356027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326943 RingCT/type: yes/0
Extra: 017a8e6dad88e39b3c876af8b0e93792a73be01eb19a3eff4d3cb519a44bb82f760211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba35d7e58a7c884c5cf7d2a62037b96788e38a840d33f15f749e3b2f80721a66 0.000600000000 1844032 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": 1356037, "vin": [ { "gen": { "height": 1356027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba35d7e58a7c884c5cf7d2a62037b96788e38a840d33f15f749e3b2f80721a66" } } ], "extra": [ 1, 122, 142, 109, 173, 136, 227, 155, 60, 135, 106, 248, 176, 233, 55, 146, 167, 59, 224, 30, 177, 154, 62, 255, 77, 60, 181, 25, 164, 75, 184, 47, 118, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: