Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6f6c52019f180cd9a1b4fec2b47e836031acfa3e1b70eb539dd0c5ef0d682e

Tx prefix hash: 0ef33013b4b47fb4bb7ee5efd482b57b0a334cbca0e53a935da4f620193b41d8
Tx public key: 7aad1bee24a04f5653d97977c39cbdaca84ef51d39d24f3f9e8eae71c5693492
Timestamp: 1690766507 Timestamp [UTC]: 2023-07-31 01:21:47 Age [y:d:h:m:s]: 03:107:17:55:35
Block: 815463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 862889 RingCT/type: yes/0
Extra: 017aad1bee24a04f5653d97977c39cbdaca84ef51d39d24f3f9e8eae71c5693492021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.001219081311 xmr

stealth address amount amount idx tag
00: 7201b31f753765f6a5f2f19fc0aa0afa92050ccf1227956973a915b79e2a0e21 0.001219081311 1267260 of 0 -

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": 815473, "vin": [ { "gen": { "height": 815463 } } ], "vout": [ { "amount": 1219081311, "target": { "key": "7201b31f753765f6a5f2f19fc0aa0afa92050ccf1227956973a915b79e2a0e21" } } ], "extra": [ 1, 122, 173, 27, 238, 36, 160, 79, 86, 83, 217, 121, 119, 195, 156, 189, 172, 168, 78, 245, 29, 57, 210, 79, 63, 158, 142, 174, 113, 197, 105, 52, 146, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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: