Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed3ea2535f6b58b545d08202c2af6836738382d7ca05709dd0ae425a2f16460a

Tx prefix hash: fda34eaa3082e55159f5a54d729e366a4d5f9ec1dab0753a2a52ea0d871f9f6c
Tx public key: 59f3f8c616c0e136e95e537288ebf5b6c28bb810e492a28686ca0f2099fb30d2
Timestamp: 1647735519 Timestamp [UTC]: 2022-03-20 00:18:39 Age [y:d:h:m:s]: 04:053:21:31:46
Block: 462161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1069467 RingCT/type: yes/0
Extra: 0159f3f8c616c0e136e95e537288ebf5b6c28bb810e492a28686ca0f2099fb30d202110000000abf7ee4e7000000000000000000

1 output(s) for total of 0.018057973684 xmr

stealth address amount amount idx tag
00: 6320397c6a2fb87257b15c2018b40323749bd17d35dc7b7de9029bdd6911d88e 0.018057973684 879556 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": 462171, "vin": [ { "gen": { "height": 462161 } } ], "vout": [ { "amount": 18057973684, "target": { "key": "6320397c6a2fb87257b15c2018b40323749bd17d35dc7b7de9029bdd6911d88e" } } ], "extra": [ 1, 89, 243, 248, 198, 22, 192, 225, 54, 233, 94, 83, 114, 136, 235, 245, 182, 194, 139, 184, 16, 228, 146, 162, 134, 134, 202, 15, 32, 153, 251, 48, 210, 2, 17, 0, 0, 0, 10, 191, 126, 228, 231, 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: