Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58aa6e1faa27110214d0cce79e4a184a22b33db22fd05d31df911f1f540ab7a6

Tx prefix hash: 3810e2d11f9a0e48d92051fc169acc108a49d5b2a4eaad61318eb7f9719c132d
Tx public key: 8f03e7f3b681bd3ab2e0bfe26acb02809f89e3ae58942a6c836ba0bc1b957992
Timestamp: 1666558289 Timestamp [UTC]: 2022-10-23 20:51:29 Age [y:d:h:m:s]: 04:027:05:53:06
Block: 615493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1066086 RingCT/type: yes/0
Extra: 018f03e7f3b681bd3ab2e0bfe26acb02809f89e3ae58942a6c836ba0bc1b95799202110000000133af99f4000000000000000000

1 output(s) for total of 0.005605524109 xmr

stealth address amount amount idx tag
00: b1301b2023cd0572e145160d28f497d279668e3a6237e71f2f368ed9a8e3eb38 0.005605524109 1052962 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": 615503, "vin": [ { "gen": { "height": 615493 } } ], "vout": [ { "amount": 5605524109, "target": { "key": "b1301b2023cd0572e145160d28f497d279668e3a6237e71f2f368ed9a8e3eb38" } } ], "extra": [ 1, 143, 3, 231, 243, 182, 129, 189, 58, 178, 224, 191, 226, 106, 203, 2, 128, 159, 137, 227, 174, 88, 148, 42, 108, 131, 107, 160, 188, 27, 149, 121, 146, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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: