Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722010f957e586ebeee95a8c65b83108bb22c19a79ebe6c9975aadda08953611

Tx prefix hash: 0768fd1657de81756abd573f7ea0488e28ff63af7968f6a34420b0aa75986e5c
Tx public key: 988a1402778aa474cb419186e07d46e6eab51d287f6c557b95f2768855d147ea
Timestamp: 1744292223 Timestamp [UTC]: 2025-04-10 13:37:03 Age [y:d:h:m:s]: 01:219:10:06:11
Block: 1258452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420792 RingCT/type: yes/0
Extra: 01988a1402778aa474cb419186e07d46e6eab51d287f6c557b95f2768855d147ea0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a694f2557d4a74196c41f6e4e2a2026ed3d09a7b08a5ce5ce55eeda8c6f87fe 0.000600000000 1745585 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": 1258462, "vin": [ { "gen": { "height": 1258452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a694f2557d4a74196c41f6e4e2a2026ed3d09a7b08a5ce5ce55eeda8c6f87fe" } } ], "extra": [ 1, 152, 138, 20, 2, 119, 138, 164, 116, 203, 65, 145, 134, 224, 125, 70, 230, 234, 181, 29, 40, 127, 108, 85, 123, 149, 242, 118, 136, 85, 209, 71, 234, 2, 17, 0, 0, 0, 5, 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: