Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fadced54745b116cdbacb73e06fa609f8f965a0a490aad7faff1bb7ea55c1f2

Tx prefix hash: 92f170be09e05bed8fef05b5fba09f955fa69ef4fef44ba3abf84fba0d9b8c55
Tx public key: 0e35116993c9412a5975573d893d7aa00be56c5c56140ba7f3dbc74e339d263d
Timestamp: 1722943254 Timestamp [UTC]: 2024-08-06 11:20:54 Age [y:d:h:m:s]: 02:100:15:16:15
Block: 1081954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596623 RingCT/type: yes/0
Extra: 010e35116993c9412a5975573d893d7aa00be56c5c56140ba7f3dbc74e339d263d02110000000991e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfbb0615986f4b62a6ee77ed66861ea314007b628e9928bbc4a8570d60cc65ce 0.000600000000 1555777 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": 1081964, "vin": [ { "gen": { "height": 1081954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfbb0615986f4b62a6ee77ed66861ea314007b628e9928bbc4a8570d60cc65ce" } } ], "extra": [ 1, 14, 53, 17, 105, 147, 201, 65, 42, 89, 117, 87, 61, 137, 61, 122, 160, 11, 229, 108, 92, 86, 20, 11, 167, 243, 219, 199, 78, 51, 157, 38, 61, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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: